From: "Dan Conti" <danc@fullplaymedia.com>
To: <gdb@sources.redhat.com>
Subject: debugging gcc 3.x c++
Date: Tue, 12 Feb 2002 14:00:00 -0000 [thread overview]
Message-ID: <D8DFF0AFE792914996F997E68FEC3A482AE4B1@bunker.iobjects.com> (raw)
Hi, i had ran into this bug before with gcc 3.0.3 and gdb 5.1, and was
told that it was properly fixed in the current versions of gdb (to be
specific, i was told that it was fixed in cvs between the 5.1 and 5.1.1
release). In the cvs snapshot i checked and the 5.1.1 release, it's
fixed in some but not all instances.
Basically when i go to print some of my C++ classes in the debugger, i
get a message saying "Value can't be converted to integer." There's a PR
filed on this at:
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&dat
abase=gdb&pr=243
Personally i am using a arm-elf cross toolchain, gcc 3.0.3 and gdb 5.1.1
on a cygwin host.
I have no problem fixing this myself if someone could point me in the
right direction, since i'm not really familiar with gdb internals.
Also, something i'm not clear on, according to the gdb mailing lists
page, 'gdb-prs' is a "Mailing list for discussing bugs submitted to the
bug reporting database", but for some reason i can't post to this list
about a bug submitted to the bug reporting database. Perhaps the
description should mention that it's for testers only (i'm assuming this
is the case?) ?
--
Dan Conti
danc@fullplaymedia.com
next reply other threads:[~2002-02-12 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 14:00 Dan Conti [this message]
2002-02-12 14:33 ` Daniel Jacobowitz
2002-02-12 15:02 Dan Conti
2002-02-12 16:53 ` 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=D8DFF0AFE792914996F997E68FEC3A482AE4B1@bunker.iobjects.com \
--to=danc@fullplaymedia.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