gdb.threads/signal-command-handle-nopass.exp: Add comment

Explain why we do "info threads".

gdb/testsuite/
2014-07-30  Pedro Alves  <palves@redhat.com>

	* gdb.threads/signal-command-handle-nopass.exp (test): Add
	comment.

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index a90ee8b4b725a49345150a8e716a3ead2b2a924f..6eb8f3eb97a6d432d428d8c699323ed3979ad1af 100644 (file)
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,8 @@
+2014-07-30  Pedro Alves  <palves@redhat.com>
+
+       * gdb.threads/signal-command-handle-nopass.exp (test): Add
+       comment.
+
 2014-07-29  Yao Qi  <yao@codesourcery.com>
 
        PR gdb/17206

diff --git a/gdb/testsuite/gdb.threads/signal-command-handle-nopass.exp b/gdb/testsuite/gdb.threads/signal-command-handle-nopass.exp
index 3ea9cf8ba5666d346e5811c1f471fdbd127bee89..e46a0ab6f079dba44f85fec024c45d262bc9ef45 100644 (file)
--- a/gdb/testsuite/gdb.threads/signal-command-handle-nopass.exp
+++ b/gdb/testsuite/gdb.threads/signal-command-handle-nopass.exp
@@ -69,6 +69,10 @@ proc test { step_over } {
 
        gdb_test "signal SIGUSR1" "handler .*"
 
+       # Make sure it was thread 1 that got the signal.  Note we list
+       # all threads instead of just thread 1, so that if something
+       # goes wrong and another thread ends up selected, we can
+       # easily see which in the logs.
        gdb_test "info threads" $pattern "thread 1 got the signal"
     }
 }