Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Cc: fnasser@redhat.com, insight@sources.redhat.com
Subject: [RFA/testsuite] Update selftest.exp
Date: Mon, 21 Oct 2002 19:07:00 -0000	[thread overview]
Message-ID: <20021022020730.GA22928@nevyn.them.org> (raw)

Are others seeing this failure?  If not, I'm not sure why not.  There is no
main in "main.c" any more.  It's in "gdb.c" now.

The "read" was bogus, too.  It was supposed to match a read syscall; what it
was actually matching was some debugging info that said "readline/".  We
call poll for the event loop nowadays.

Is this patch OK?  Should I also match "gdbtk-main.c" [I don't know if this
part of the testsuite is ever run on the insight binary]?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

2002-10-21  Daniel Jacobowitz  <drow@mvista.com>

	* gdb.base/selftest.exp: Update for current gdb.

Index: testsuite/gdb.base/selftest.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/selftest.exp,v
retrieving revision 1.4
diff -u -p -r1.4 selftest.exp
--- testsuite/gdb.base/selftest.exp	22 Jun 2002 22:19:37 -0000	1.4
+++ testsuite/gdb.base/selftest.exp	13 Oct 2002 22:55:02 -0000
@@ -392,7 +392,7 @@ GDB.*Copyright \[0-9\]+ Free Software Fo
     set description "backtrace through signal handler"
     send_gdb "backtrace\n"
     gdb_expect {
-	-re "#0.*read.*in main \\(.*\\) at .*main\\.c.*$gdb_prompt $" {
+	-re "#0.*(read|poll).*in main \\(.*\\) at .*gdb\\.c.*$gdb_prompt $" {
 	    pass "$description"
 	}
 	-re ".*$gdb_prompt $" {


             reply	other threads:[~2002-10-22  2:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21 19:07 Daniel Jacobowitz [this message]
2002-10-22 10:09 ` Keith Seitz
2002-11-05 13:44 ` Daniel Jacobowitz
2002-12-02 21:08   ` Daniel Jacobowitz
2002-12-03  7:20   ` Fernando Nasser
2002-12-02 21:57 Michael Elizabeth Chastain

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=20021022020730.GA22928@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=insight@sources.redhat.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