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

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