From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18508 invoked by alias); 16 Jan 2003 00:17:08 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 18404 invoked from network); 16 Jan 2003 00:17:05 -0000 Received: from unknown (HELO jackfruit.Stanford.EDU) (171.64.38.136) by sources.redhat.com with SMTP; 16 Jan 2003 00:17:05 -0000 Received: (from carlton@localhost) by jackfruit.Stanford.EDU (8.11.6/8.11.6) id h0G0H0I30516; Wed, 15 Jan 2003 16:17:00 -0800 X-Authentication-Warning: jackfruit.Stanford.EDU: carlton set sender to carlton@math.stanford.edu using -f To: gdb@sources.redhat.com Cc: Elena Zannoni , Fernando Nasser Subject: zillions of testsuite failures From: David Carlton Date: Thu, 16 Jan 2003 00:17:00 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-01/txt/msg00279.txt.bz2 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 /testsuite/gdb.base/args 1 '' '' 3 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