From: Tom Tromey <tromey@redhat.com>
To: Chris Moller <cmoller@redhat.com>
Cc: Project Archer <archer@sourceware.org>
Subject: Re: vtable?
Date: Tue, 19 Jan 2010 22:33:00 -0000 [thread overview]
Message-ID: <m33a213eue.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4B55DA8A.30307@redhat.com> (Chris Moller's message of "Tue, 19 Jan 2010 11:15:06 -0500")
>>>>> "Chris" == Chris Moller <cmoller@redhat.com> writes:
Chris> So the question is whether the right thing to do is fix the gdb a
Chris> priori information hack, or to fix gcc (if necessary--a DWARF dump of
Chris> the testcase shows a lot of information concerning all of the relevant
Chris> classes, but whether it's right or sufficient I don't know) and fix
Chris> gdb properly to use the DWARF info.
Fix gdb's current approach. The ABI is pretty stable, and gdb already
uses it for a lot of things.
Tom
next prev parent reply other threads:[~2010-01-19 22:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 18:01 vtable? Chris Moller
2010-01-14 20:11 ` vtable? Tom Tromey
2010-01-14 20:30 ` vtable? Chris Moller
2010-01-19 16:15 ` vtable? Chris Moller
2010-01-19 22:33 ` Tom Tromey [this message]
2010-01-20 8:44 ` vtable? Chris Moller
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=m33a213eue.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
--cc=cmoller@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).