* 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.

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index bfe41df..1c47de2 100644 (file)
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -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.

diff --git a/gdb/testsuite/gdb.threads/linux-dp.exp b/gdb/testsuite/gdb.threads/linux-dp.exp
index 4032f2d..f4b2af0 100644 (file)
--- a/gdb/testsuite/gdb.threads/linux-dp.exp
+++ b/gdb/testsuite/gdb.threads/linux-dp.exp
@@ -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.