From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: [Bug#203553: gdb: Assertion fails on -data-list-changed-registers]
Date: Wed, 30 Jul 2003 22:06:00 -0000 [thread overview]
Message-ID: <20030730220603.GA16187@nevyn.them.org> (raw)
Huh, we can't even print out the error message correctly, apparently.
Does this look familiar to anyone?
----- Forwarded message from Kim Hansen <k-grov@oek.dk> -----
Date: Wed, 30 Jul 2003 23:49:33 +0200
From: Kim Hansen <k-grov@oek.dk>
Subject: Bug#203553: gdb: Assertion fails on -data-list-changed-registers
To: Debian Bug Tracking System <submit@bugs.debian.org>
Reply-To: Kim Hansen <k-grov@oek.dk>, 203553@bugs.debian.org
X-Mailer: reportbug 2.20
Package: gdb
Version: 5.3.20030629-2
Severity: normal
The GDB/MI-command '-data-list-changed-registers' doesn't work, see the
log:
kim@grov:~$ gdb --interpreter=mi -q
(gdb)
-data-list-changed-registers
~"/nevyn/local/gdb/gdb-5.3.20030629/gdb/frame.c:601: internal-error:
\301\005\036\b@\t\036\b*: Assertion `(null)' failed.\n"
~"A problem internal to GDB has been detected,\n"
~"further debugging may prove unreliable.\n"
~"Quit this debugging session? (y or n) "
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux grov 2.4.21-pre4-13 #1 Fri May 9 13:07:15 CEST 2003 i686
Locale: LANG=C, LC_CTYPE=da_DK
Versions of packages gdb depends on:
ii libc6 2.3.1-17 GNU C Library: Shared libraries an
ii libncurses5 5.3.20030719-1 Shared libraries for terminal hand
ii libreadline4 4.3-5 GNU readline and history libraries
-- no debconf information
----- End forwarded message -----
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2003-07-30 22:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 22:06 Daniel Jacobowitz [this message]
2003-07-31 1:04 ` Alain Magloire
2003-07-31 22:44 ` Andrew Cagney
2003-08-01 16:52 ` Daniel Jacobowitz
2003-08-02 0:19 ` Andrew Cagney
2003-08-02 0:38 ` Daniel Jacobowitz
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=20030730220603.GA16187@nevyn.them.org \
--to=drow@mvista.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).