From: Daniel Jacobowitz <drow@false.org>
To: gdb@sources.redhat.com
Subject: Odd test failures - weird.exp, mi-cli.exp
Date: Mon, 19 Apr 2004 03:45:00 -0000 [thread overview]
Message-ID: <20040419031150.GA14124@nevyn.them.org> (raw)
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
next reply other threads:[~2004-04-19 3:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 3:45 Daniel Jacobowitz [this message]
2004-04-19 7:38 ` Daniel Jacobowitz
2004-04-20 13:46 ` Mark Kettenis
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=20040419031150.GA14124@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).