public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@kealia.com>
Cc: gdb <gdb@sources.redhat.com>, Elena Zannoni <ezannoni@redhat.com>,
	Jim Blandy <jimb@redhat.com>
Subject: Re: DW_AT_specification and partial symtabs
Date: Thu, 12 Jun 2003 17:05:00 -0000	[thread overview]
Message-ID: <20030612170545.GA16995@nevyn.them.org> (raw)
In-Reply-To: <m3el1zfcwd.fsf@dhcp-10-42-69-238.kealia.com>

On Thu, Jun 12, 2003 at 10:01:38AM -0700, David Carlton wrote:
> One of the main issues that I'm dealing with on my branch is getting
> nested types to work right in C++ (with DWARF 2): these have the
> characteristic that they depend on the hierarchical structure of the
> debug info to a greater extent than, as far as I can tell, anything
> that mainline GDB currently does.  The reason for this is that, to
> deduce a nested type's name, you really have to know where it lives in
> the hierarchical structure, so you can add whatever prefixes are
> appropriate to its DW_AT_name.  (With non-types, we (over)use mangled
> names for this sort of thing, so it's not such a big deal there.)

> Unfortunately, there's no way to get at that information at all with
> the current psymtab reader: it tries to march from top-level DIE to
> top-level DIE without building up a tree of DIEs.  So it seems to me
> that I have no choice but to have the psymtab reader build up a tree
> of DIEs before it starts reading, just like the symtab reader does.
> 
> Comments?  Suggestions?  Ideas for how to make the tree that the
> psymtab reader builds to be as small as possible?  I'm a little
> worried about weird cases like local classes: if I have

I'll answer this in more depth in a bit.  For now, something to
consider: I would like to add .debug_typenames (spelling?) to GCC -
it's an SGI extension, IIRC.  This plus .debug_pubnames should allow us
to implement psymtabs entirely without mapping .debug_info.  I believe
it handles your case too, since it should have fully qualified
typenames.

The implementation may need a little tweaking for space efficiency...

>   void foo ()
>   {
>     class Local {
>     public:
>       int mem() {return 1;}
>     };
> 
>     ...
>   }
> 
> then is the compiler allowed to put a definition of Local::mem as a
> child of the comp unit die (with a DW_AT_specification pointing to a
> DIE inside of foo somewhere)?

I believe so.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-12 17:01 David Carlton
2003-06-12 17:05 ` Daniel Jacobowitz [this message]
2003-06-12 17:10   ` David Carlton
2003-06-12 17:20   ` Elena Zannoni
2003-06-12 22:17     ` David Carlton
2003-06-13 13:36       ` Daniel Jacobowitz
2003-06-13 14:00         ` Elena Zannoni
2003-06-13 15:38           ` Andrew Cagney
2003-06-13 15:50             ` Daniel Jacobowitz
2003-06-13 15:57               ` Andrew Cagney
2003-06-13 16:24               ` Andrew Cagney
2003-06-13 16:34                 ` Daniel Jacobowitz
2003-06-17  0:09             ` David Carlton

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=20030612170545.GA16995@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=carlton@kealia.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@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).