From: Jason Merrill <jason@redhat.com>
To: libstdc++@gcc.gnu.org
Cc: gdb@sources.redhat.com
Subject: Re: C++ debugging progress
Date: Wed, 28 Nov 2001 01:31:00 -0000 [thread overview]
Message-ID: <wvl667v1btw.fsf@prospero.cambridge.redhat.com> (raw)
Message-ID: <20011128013100.PmfhHdMHHwrNDTQhAN_C0f7zOPZ1YnHj2eGzpEr1Kys@z> (raw)
In-Reply-To: <20011128020256.A9688@nevyn.them.org>
>>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:
> I'll not be posting the patches for another day or two. The way I do it now
> is grossly inefficient; I look through RTTI at every lookup instead of once
> per type. It also depends on presence of RTTI. There's not much I can do
> about that - or rather, I could, but AFAICT it would require walking the
> inheritance graph in the proper order and I don't have the machinery to do
> that easily. I'm not heartbroken that we need RTTI for debugging though.
So you're using the inheritance information in the RTTI rather than the debug
info? That seems unfortunate. I'm not sure why you would need to worry
about ordering; the debug info should tell you exactly where things are.
If it doesn't, it should probably be fixed.
Jason
next prev parent reply other threads:[~2001-11-28 1:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 23:03 Daniel Jacobowitz
2001-11-18 21:43 ` Daniel Jacobowitz
2001-11-19 9:04 ` Benjamin Kosnik
2001-11-27 23:36 ` Benjamin Kosnik
2001-11-19 11:16 ` Daniel Berlin
2001-11-21 13:37 ` Dan Mosedale
2001-11-28 12:25 ` Dan Mosedale
2001-11-27 23:43 ` Daniel Berlin
2001-11-19 13:41 ` Jason Merrill [this message]
2001-11-28 1:31 ` Jason Merrill
2001-11-28 9:41 ` Daniel Jacobowitz
2001-11-21 4:12 ` Daniel Jacobowitz
2001-11-21 5:06 ` Daniel Berlin
2001-11-28 10:36 ` Daniel Berlin
2001-11-28 10:49 ` Daniel Jacobowitz
2001-11-21 12:33 ` Daniel Jacobowitz
2001-11-28 11:41 ` Jason Merrill
2001-11-21 13:21 ` Jason Merrill
2001-11-21 13:42 ` Daniel Jacobowitz
2001-11-28 12:32 ` Daniel Jacobowitz
2001-11-21 16:38 ` Jason Merrill
2001-11-22 0:13 ` Daniel Jacobowitz
2001-11-24 22:52 ` Jason Merrill
2001-11-29 9:44 ` Jason Merrill
2001-11-29 12:28 ` Daniel Jacobowitz
2001-11-25 8:34 ` Daniel Jacobowitz
2001-11-25 9:01 ` Kevin Buettner
2001-11-25 10:30 ` Jason Merrill
2001-11-29 19:12 ` Jason Merrill
2001-11-29 13:11 ` Kevin Buettner
2001-11-29 12:50 ` Benjamin Kosnik
2001-11-25 8:40 ` Benjamin Kosnik
2001-11-28 13:31 ` Daniel Jacobowitz
2001-11-28 13:03 ` Jason Merrill
[not found] ` <20011128151819.A31514@nevyn.them.org>
2001-11-21 22:26 ` Jason Merrill
2001-11-28 13:14 ` Jason Merrill
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=wvl667v1btw.fsf@prospero.cambridge.redhat.com \
--to=jason@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=libstdc++@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