yggdrasil/binutils-gdb
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

* gdb.threads/linux-dp.exp: Recognize an additional message

Browse Source 
generated by GDB when it doesn't understand how to debug threads
on the target system.
This commit is contained in:
Jim Blandy 2001-03-20 15:54:34 +00:00
parent 95fc45e66f
commit 754cbe1c31
2 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,9 @@
2001-03-20 Jim Blandy <jimb@redhat.com>
* gdb.threads/linux-dp.exp: Recognize an additional message
generated by GDB when it doesn't understand how to debug threads
on the target system.
2001-03-19 Andrew Cagney <ac131313@redhat.com>
* gdb.mi/mi-console.exp: Document ``Hello'' as a known bug.

2
gdb/testsuite/gdb.threads/linux-dp.exp
View File

@ -71,7 +71,7 @@ for {set i 0} {$i < 5} {incr i} {
-re "\\\[New .*\\\].*$gdb_prompt $" {
pass "create philosopher: $i"
}
-re "Program received signal.*(Unknown signal|SIGUSR).*$gdb_prompt $" {
-re "Program received signal.*(Unknown signal|SIGUSR|Real-time event).*$gdb_prompt $" {
# It would be nice if we could catch the message that GDB prints
# when it first notices that the thread library doesn't support
# debugging, or if we could explicitly ask GDB somehow.