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

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