[RFA]: test suite: recognize GDB message for unsupported threads

[Jim Blandy <jimb@zwingli.cygnus.com>]

Without this change, the test suite hangs on Linux systems that have
real-time signals, but lack libthread-db.

2001-03-15  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.

Index: gdb/testsuite/gdb.threads/linux-dp.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.threads/linux-dp.exp,v
retrieving revision 1.2
diff -c -r1.2 linux-dp.exp
*** gdb/testsuite/gdb.threads/linux-dp.exp	2001/03/06 08:21:59	1.2
--- gdb/testsuite/gdb.threads/linux-dp.exp	2001/03/16 02:01:23
***************
*** 71,77 ****
  	-re "\\\[New .*\\\].*$gdb_prompt $" {
  	    pass "create philosopher: $i"
  	}
! 	-re "Program received signal.*(Unknown signal|SIGUSR).*$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.
--- 71,77 ----
  	-re "\\\[New .*\\\].*$gdb_prompt $" {
  	    pass "create philosopher: $i"
  	}
! 	-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.