OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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.
This commit is contained in:
Pedro Alves 2014-07-30 12:19:30 +01:00
parent a1c7835a2f
commit cc6563d29b
2 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/testsuite/ChangeLog
View File

@ -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

4
gdb/testsuite/gdb.threads/signal-command-handle-nopass.exp
View File

@ -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"
}
}