Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: Jim Blandy <jimb@cygnus.com>
Cc: gdb-patches@sources.redhat.com, Michael Snyder <msnyder@cygnus.com>
Subject: Re: [RFA]: test suite: recognize GDB message for unsupported threads
Date: Fri, 16 Mar 2001 02:08:00 -0000	[thread overview]
Message-ID: <3AB1E324.A4A1E76E@redhat.com> (raw)
In-Reply-To: <200103160237.VAA26416@zwingli.cygnus.com>

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


  reply	other threads:[~2001-03-16  2:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15 18:36 Jim Blandy
2001-03-16  2:08 ` Fernando Nasser [this message]
2001-03-16 11:28   ` Michael Snyder
2001-03-16 11:27 ` Michael Snyder
2001-03-20  7:55   ` Jim Blandy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3AB1E324.A4A1E76E@redhat.com \
    --to=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@cygnus.com \
    --cc=msnyder@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox