Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@kealia.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa/c++] cp_lookup_rtti_type, take 2
Date: Fri, 05 Dec 2003 17:12:00 -0000	[thread overview]
Message-ID: <yf2r7zjnq7u.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20031205042237.56AFD4B35C@berman.michael-chastain.com> (Michael Elizabeth Chastain's message of "Thu,  4 Dec 2003 23:22:37 -0500 (EST)")

On Thu, 4 Dec 2003 23:22:37 -0500 (EST), mec.gnu@mindspring.com
(Michael Elizabeth Chastain) said:

>> The only reason we can do it by symbol lookup at all is the One
>> Definition Rule, and we should probably be restricting ourselves to the
>> objfile in which we found the minimal symbol.

> Yes, it's still very flaky.  The only reason it works now is that
> there is a low-priority "fallback" search over all static blocks.
> That is just more trouble waiting to happen.

Yeah, but my current patch awaiting approval fixes that.  Those
symbols shouldn't be static in the first place.

> We've got a vtbl pointer, and we want type information for it.
> So we translate:

>   vtbl address -> minsym
>   minsym -> mangled name
>   mangled name -> demangled name
>   demangled name -> prefix
>   prefix -> symbol
>   symbol -> type

> Maybe we should just go from the vtbl address to the symbol without
> converting to a name and back again?!

It would be nice if we could eventually short-circuit much or all of
this.  As Daniel likes to point out, we should try to reduce our
demangler dependencies wherever possible, and this is a particularly
unpleasant one.

> In retrospect, my new lookup_rtti_type should take the domain as a
> parameter.

I think that would be more confusing.

David Carlton
carlton@kealia.com


  parent reply	other threads:[~2003-12-05 17:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-05  4:23 Michael Elizabeth Chastain
2003-12-05  5:01 ` Daniel Jacobowitz
2003-12-05 17:12 ` David Carlton [this message]
2003-12-05 17:16   ` Daniel Jacobowitz
2003-12-05 17:38     ` David Carlton
2003-12-05 17:40       ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2003-12-05  5:26 Michael Elizabeth Chastain
2003-12-01 21:40 Michael Elizabeth Chastain
2003-12-05  3:30 ` Daniel Jacobowitz
2003-12-05 16:57   ` David Carlton
2003-12-05 17:16     ` 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=yf2r7zjnq7u.fsf@hawaii.kealia.com \
    --to=carlton@kealia.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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