Blame SOURCES/bcc-0.14.0-deadlock-print-a-more-explicit-message-when-pthread_.patch

0e54f6
From c263daf925a7a74f7ae64b049cf3def8b298beee Mon Sep 17 00:00:00 2001
0e54f6
From: Jerome Marchand <jmarchan@redhat.com>
0e54f6
Date: Wed, 10 Jun 2020 10:28:42 +0200
0e54f6
Subject: [PATCH 1/4] deadlock: print a more explicit message when
0e54f6
 pthread_mutex_unlock can't be attached
0e54f6
0e54f6
Most likely, this happen because of a missing --binary argument. Let's
0e54f6
be friendly to our user and print a more useful messsage.
0e54f6
---
0e54f6
 tools/deadlock.py | 2 +-
0e54f6
 1 file changed, 1 insertion(+), 1 deletion(-)
0e54f6
0e54f6
diff --git a/tools/deadlock.py b/tools/deadlock.py
0e54f6
index 17848720..81122adb 100755
0e54f6
--- a/tools/deadlock.py
0e54f6
+++ b/tools/deadlock.py
0e54f6
@@ -483,7 +483,7 @@ import time
0e54f6
                 pid=args.pid,
0e54f6
             )
0e54f6
         except Exception as e:
0e54f6
-            print('%s. Failed to attach to symbol: %s' % (str(e), symbol))
0e54f6
+            print('%s. Failed to attach to symbol: %s\nIs --binary argument missing?' % (str(e), symbol))
0e54f6
             sys.exit(1)
0e54f6
     for symbol in args.lock_symbols:
0e54f6
         try:
0e54f6
-- 
0e54f6
2.25.4
0e54f6