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

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

[Jim Blandy]

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.

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

[Fernando Nasser]

It seems like an "obvious fix for me.

OK with you Michael Snyder?

Fernando


Jim Blandy wrote:
> 
> 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.

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

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

[Michael Snyder]

Fernando Nasser wrote:
> 
> It seems like an "obvious fix for me.
> 
> OK with you Michael Snyder?

Yep, please check it in.

> 
> Jim Blandy wrote:
> >
> > 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.
> 
> --
> Fernando Nasser
> Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
> 2323 Yonge Street, Suite #300
> Toronto, Ontario   M4P 2C9

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

[Michael Snyder]

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

Cool.  As the new but not yet announced co-maintainer for gdb thread testsuites,
I approve.  Please check it in.


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

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

[Jim Blandy]

Michael Snyder <msnyder@cygnus.com> writes:
> Jim Blandy wrote:
> > Without this change, the test suite hangs on Linux systems that have
> > real-time signals, but lack libthread-db.
> 
> Cool.  As the new but not yet announced co-maintainer for gdb thread
> testsuites, I approve.  Please check it in.

Thanks.  I've committed this.