Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@kealia.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfa/c++] cp_lookup_rtti_type, take 2
Date: Fri, 05 Dec 2003 17:38:00 -0000	[thread overview]
Message-ID: <yf2llprnp03.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20031205171658.GB27834@nevyn.them.org> (Daniel Jacobowitz's message of "Fri, 5 Dec 2003 12:16:58 -0500")

On Fri, 5 Dec 2003 12:16:58 -0500, Daniel Jacobowitz <drow@mvista.com> said:

> How do you suggest we do it?  Some new addition to the debug info?  I
> don't believe we have anything at the moment that fills this need.

Hmm.  I thought I'd seen something appropriate in the debug info, but
now I realize that I was looking for the slot for the vtable in the
class, which is a quite different matter.

Well, here's what I see when looking for a vtable symbol in a sample
file:

	.uleb128 0x1d	# (DIE (0x20d) DW_TAG_variable)
	.long	.LC9	# DW_AT_name: "_ZTI1C"
	.long	0x21e	# DW_AT_type
	.byte	0x1	# DW_AT_external
	.byte	0x1	# DW_AT_artificial
	.byte	0x5	# DW_AT_location
	.byte	0x3	# DW_OP_addr
	.long	_ZTI1C

So DW_TAG_variable + DW_AT_artificial is a start - looking for that
(plus perhaps guiltily peeking at the demanged name just to make sure
it starts with 'typeinfo') lets us find the vtable symbols.  But that
doesn't help - the DW_AT_type doesn't actually lead us to the type
that it's the vtable for, and certainly none of the other attributes
are going to help.

Sigh.

David Carlton
carlton@kealia.com


  reply	other threads:[~2003-12-05 17:38 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
2003-12-05 17:16   ` Daniel Jacobowitz
2003-12-05 17:38     ` David Carlton [this message]
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=yf2llprnp03.fsf@hawaii.kealia.com \
    --to=carlton@kealia.com \
    --cc=gdb-patches@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