public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: James Cownie <jcownie@etnus.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7081: DWARF enhancements for C++
Date: Thu, 20 Jun 2002 10:16:00 -0000 [thread overview]
Message-ID: <20020620164603.2919.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/7081; it has been noted by GNATS.
From: James Cownie <jcownie@etnus.com>
To: gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: c++/7081: DWARF enhancements for C++
Date: Thu, 20 Jun 2002 17:36:01 +0100
> This one isn't really necessary. The ABI specifies where the vtable
> pointer will be, and GDB is quite capable of using that knowledge to
> identify the runtime type. I believe even 'whatis' will do this for
> you. Whichever debugger you're using must have an understanding of the
> binary's ABI to debug C++ anyway...
Requiring that the debugger know this from the ABI (rather than being
told it by the compiler) is exactly why it takes a long time for
debuggers to catch up when the compiler ABI is changed :-(
-- Jim
James Cownie <jcownie@etnus.com>
Etnus, LLC. +44 117 9071438
http://www.etnus.com
next reply other threads:[~2002-06-20 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 10:16 James Cownie [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-20 9:46 Daniel Jacobowitz
2002-06-20 3:06 jcownie
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=20020620164603.2919.qmail@sources.redhat.com \
--to=jcownie@etnus.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/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).