This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[RFA/testsuite] Update selftest.exp


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 $" {


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]