From: David Carlton <carlton@math.stanford.edu>
To: gdb <gdb@sources.redhat.com>
Cc: Andrew Cagney <ac131313@redhat.com>
Subject: gdb.mi/mi-cli.exp failures
Date: Mon, 31 Mar 2003 19:35:00 -0000 [thread overview]
Message-ID: <ro14r5j1g87.fsf@jackfruit.Stanford.EDU> (raw)
[ I just got back from vacation, so my apologies if I've missed some
discussion relevant to this. ]
I'm getting a testsuite failure on gdb.mi/mi-cli.exp: the relevant bit
of gdb.log is as follows:
888-interpreter-exec console "set $pc=0x0"
&"frame.c:62: internal-error: get_frame_id: Assertion `!legacy_frame_p (current_gdbarch)' failed.\n"
&"A problem internal to GDB has been detected. Further\ndebugging may prove unreliable.\n"
ERROR: Process no longer exists
UNRESOLVED: gdb.mi/mi-cli.exp: -interpreter-exec console "set $pc=0x0"
testcase ./gdb.mi/mi-cli.exp completed in 1 seconds
This is with GDB updated an hour or so ago, with i686-pc-linux-gnu,
GCC 3.1, DWARF 2.
David Carlton
carlton@math.stanford.edu
next reply other threads:[~2003-03-31 19:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 19:35 David Carlton [this message]
2003-03-31 20:22 ` Andrew Cagney
2003-03-31 21:08 ` Andrew Cagney
2003-03-31 21:20 ` Andrew Cagney
2003-04-01 1:09 ` Hans-Peter Nilsson
2003-04-01 1:38 ` Ian Lance Taylor
2003-04-01 10:18 ` Nick Clifton
2003-04-01 15:08 ` Andrew Cagney
2003-04-01 15:18 ` Daniel Jacobowitz
2003-04-01 16:22 ` Andrew Cagney
2003-04-01 16:34 ` Daniel Jacobowitz
2003-04-01 17:01 ` Andrew Cagney
2003-04-01 18:03 ` Daniel Jacobowitz
[not found] ` <m31y0mxk8i.fsf@workshop.nickc.cambridge.redhat.com>
2003-04-01 17:09 ` Andrew Cagney
2003-04-01 18:23 ` Daniel Jacobowitz
2003-04-02 17:06 ` Nick Clifton
2003-04-02 17:13 ` Daniel Jacobowitz
2003-04-02 17:21 ` Ian Lance Taylor
2003-04-02 17:28 ` Daniel Jacobowitz
2003-04-02 17:44 ` Ian Lance Taylor
2003-04-02 18:05 ` Daniel Jacobowitz
2003-04-02 20:39 ` Ian Lance Taylor
2003-04-02 20:38 ` Daniel Jacobowitz
2003-04-02 20:53 ` Ian Lance Taylor
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=ro14r5j1g87.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=ac131313@redhat.com \
--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).