This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: zillions of testsuite failures
- From: Elena Zannoni <ezannoni at redhat dot com>
- To: David Carlton <carlton at math dot stanford dot edu>
- Cc: gdb at sources dot redhat dot com, Elena Zannoni <ezannoni at redhat dot com>, Fernando Nasser <fnasser at redhat dot com>
- Date: Wed, 15 Jan 2003 19:35:38 -0500
- Subject: Re: zillions of testsuite failures
- References: <ro165sq6j9h.fsf@jackfruit.Stanford.EDU>
David Carlton writes:
> Is anybody seeing lots of testsuite failures all of a sudden? I'm
> getting huge numbers; many, possibly all of them (e.g. every MI test
> fails), seem to have to do with how GDB is invoked. It seems like, at
> some point, invocations start getting
>
> <directory>/testsuite/gdb.base/args 1 '' '' 3
>
Argh! that's my fault!!! Sorry.
Let me fix it.
I think I set a global and didn't reset it....
Elena
> tacked onto them. E.g. the last line of gdb.sum is:
>
> /extra/gdb/mirror/src/gdb/testsuite/../../gdb/gdb version 2003-01-15-cvs --args /extra/gdb/mirror/src/gdb/testsuite/gdb.base/args 1 '' '' 3
>
> Looking at this a bit further, it seems like this 'global GDBFLAGS' that
> args.exp sets is persisting for the rest of the entire test run. So I
> think there's something wrong with args.exp.
>
> On a separate, I get the following results from gdb.base/advance.exp
>
> Running ./gdb.base/advance.exp ...
> PASS: gdb.base/advance.exp: advance line number
> PASS: gdb.base/advance.exp: malformed advance
> PASS: gdb.base/advance.exp: advance func
> FAIL: gdb.base/advance.exp: advance function not called by current frame
> FAIL: gdb.base/advance.exp: find line number containing "break here"
> PASS: gdb.base/advance.exp: set breakpoint at call to func3
> FAIL: gdb.base/advance.exp: continue to call to func3 in main
> FAIL: gdb.base/advance.exp: advance function called as param
> FAIL: gdb.base/advance.exp: advance with no argument
>
> This happens before the args fiasco, so I think the failures are
> legit. Are they known? I'll append the relevant part of my gdb.log
> after my signature.
>
> David Carlton
> carlton@math.stanford.edu
>
> (gdb) run
> Starting program: /extra/gdb/mirror/src/gdb/testsuite/gdb.base/advance
>
> Breakpoint 1, main () at gdb.base/advance.c:37
> 37 c = 5;
> (gdb) list ./gdb.base/advance.c:1,1
> No source file named ./gdb.base/advance.c.
> (gdb) search advance this location
> 38 b = 3; /* advance this location */
> (gdb) advance 38
> main () at gdb.base/advance.c:38
> 38 b = 3; /* advance this location */
> (gdb) PASS: gdb.base/advance.exp: advance line number
> list ./gdb.base/advance.c:1,1
> No source file named ./gdb.base/advance.c.
> (gdb) search advance malformed
> 43 return 0; /* advance malformed */
> (gdb) advance 43 then stop
> Junk at end of arguments.
> (gdb) PASS: gdb.base/advance.exp: malformed advance
> advance func
> func () at gdb.base/advance.c:18
> 18 x = x + 5;
> (gdb) PASS: gdb.base/advance.exp: advance func
> advance func3
> main () at gdb.base/advance.c:41
> 41 func3 (); /* break here */
> (gdb) FAIL: gdb.base/advance.exp: advance function not called by current frame
> list ./gdb.base/advance.c:1,1
> No source file named ./gdb.base/advance.c.
> (gdb) search break here
> Expression not found
> (gdb) FAIL: gdb.base/advance.exp: find line number containing "break here"
> break -1
> Breakpoint 2 at 0x80484aa: file gdb.base/advance.c, line 40.
> (gdb) PASS: gdb.base/advance.exp: set breakpoint at call to func3
> continue
> Continuing.
>
> Program exited normally.
> (gdb) FAIL: gdb.base/advance.exp: continue to call to func3 in main
> advance foo
> The program is not running.
> (gdb) FAIL: gdb.base/advance.exp: advance function called as param
> advance
> The program is not running.
> (gdb) FAIL: gdb.base/advance.exp: advance with no argument