From: David Carlton <carlton@kealia.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: GDB <gdb@sources.redhat.com>
Subject: Re: gdb can't handle a DIE with both sibling and children
Date: Thu, 31 Jul 2003 18:19:00 -0000 [thread overview]
Message-ID: <yf2d6fqzhh2.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20030731181355.GA14242@lucon.org> (H. J. Lu's message of "Thu, 31 Jul 2003 11:13:55 -0700")
On Thu, 31 Jul 2003 11:13:55 -0700, "H. J. Lu" <hjl@lucon.org> said:
> It is entirely possible for a DIE with both sibling and children. But
> scan_partial_symbols () has
> /* If the die has a sibling, skip to the sibling. Do not skip
> enumeration types, we want to record their enumerators. Do
> not skip namespaces, we want to record symbols inside
> them. */
> if (pdi.sibling
> && pdi.tag != DW_TAG_enumeration_type
> && pdi.tag != DW_TAG_namespace)
> {
> info_ptr = pdi.sibling;
> }
> else if (pdi.has_children)
> {
> /* Die has children, but either the optional DW_AT_sibling
> attribute is missing or we want to look at them. */
> nesting_level++;
> }
The partial symbol table normally only contains info about top-level
symbols; so scan_partial_symbols rarely wants to look at children at
all. The full symbol table contains info about everything, though.
Is this causing you a problem in some specific situation?
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2003-07-31 18:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 18:13 H. J. Lu
2003-07-31 18:19 ` David Carlton [this message]
2003-07-31 18:20 ` Daniel Jacobowitz
2003-07-31 18:27 ` H. J. Lu
2003-07-31 18:47 ` Daniel Jacobowitz
2003-07-31 19:36 ` David Carlton
2003-07-31 19:56 ` H. J. Lu
2003-07-31 20:02 ` Daniel Jacobowitz
2003-07-31 20:22 ` H. J. Lu
2003-07-31 20:29 ` Daniel Jacobowitz
2003-07-31 20:58 ` H. J. Lu
2003-07-31 21:01 ` Daniel Jacobowitz
2003-07-31 20:29 ` David Carlton
2003-07-31 20:13 ` David Carlton
2003-07-31 20:37 Michael Elizabeth Chastain
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=yf2d6fqzhh2.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=gdb@sources.redhat.com \
--cc=hjl@lucon.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