From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31814 invoked by alias); 19 Apr 2004 03:11:57 -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 31801 invoked from network); 19 Apr 2004 03:11:55 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 19 Apr 2004 03:11:55 -0000 Received: from drow by nevyn.them.org with local (Exim 4.32 #1 (Debian)) id 1BFPCI-0005rQ-5L for ; Sun, 18 Apr 2004 23:11:50 -0400 Date: Mon, 19 Apr 2004 03:45:00 -0000 From: Daniel Jacobowitz To: gdb@sources.redhat.com Subject: Odd test failures - weird.exp, mi-cli.exp Message-ID: <20040419031150.GA14124@nevyn.them.org> Mail-Followup-To: gdb@sources.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-04/txt/msg00102.txt.bz2 Three more failures for i686-pc-linux-gnu have appeared in the last few days on my test system. FAIL: gdb.mi/mi-cli.exp: -interpreter-exec console "set $pc=0x0" FAIL: gdb.mi/mi2-cli.exp: -interpreter-exec console "set $pc=0x0" FAIL: gdb.stabs/weird.exp: Errors reading weirdx.o It's not completely clear whether they are gdb bugs or test bugs. Here's the log entries: 888-interpreter-exec console "set $pc=0x0" &"Previous frame inner to this frame (corrupt stack?)\n" 888^error,msg="Previous frame inner to this frame (corrupt stack?)" (gdb) FAIL: gdb.mi/mi-cli.exp: -interpreter-exec console "set $pc=0x0" This is at test bug - it's pretty funny, actually. The error is correct, but depends on the precise garbage on the stack when we set the PC to zero - in my case, if LD_LIBRARY_PATH contains the three items that the in-tree expect-bld.sh wrapper puts there, then we'll get an error. What's this trying to test, and is there some better way? (gdb) file object.o Reading symbols from /opt/src/binutils/x86-as/gdb/testsuite/object.o...done. Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (gdb) FAIL: gdb.stabs/weird.exp: Errors reading weirdx.o I can't figure out what causes this. Presumably it is griping about the libthread_db message, but GDB 6.1 appears to generate the same thing, and I haven't been getting this failure in the past. Does anyone else see this? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer