From cc6563d29b6f86b23c4f9a8ea73dabf9f7fc0d91 Mon Sep 17 00:00:00 2001 From: Pedro Alves Date: Wed, 30 Jul 2014 12:19:30 +0100 Subject: [PATCH] gdb.threads/signal-command-handle-nopass.exp: Add comment Explain why we do "info threads". gdb/testsuite/ 2014-07-30 Pedro Alves * gdb.threads/signal-command-handle-nopass.exp (test): Add comment. --- gdb/testsuite/ChangeLog | 5 +++++ gdb/testsuite/gdb.threads/signal-command-handle-nopass.exp | 4 ++++ 2 files changed, 9 insertions(+) diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog index a90ee8b4b72..6eb8f3eb97a 100644 --- a/gdb/testsuite/ChangeLog +++ b/gdb/testsuite/ChangeLog @@ -1,3 +1,8 @@ +2014-07-30 Pedro Alves + + * gdb.threads/signal-command-handle-nopass.exp (test): Add + comment. + 2014-07-29 Yao Qi 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 3ea9cf8ba56..e46a0ab6f07 100644 --- 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" } } -- 2.30.2