Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Manoj Iyer <manjo@austin.ibm.com>,
	gdb-patches@sources.redhat.com,
	Elena Zannoni <ezannoni@redhat.com>
Subject: Re: [RFC] Dont skip DW_TAG_member in load_partial_dies()
Date: Wed, 16 Feb 2005 22:50:00 -0000	[thread overview]
Message-ID: <20050216190824.GU1200@adacore.com> (raw)
In-Reply-To: <20050216001647.GA10512@nevyn.them.org>

Hello Daniel,

> > Just FYI: Here is the change we've made so far in gdb-6.3.
> > 
> >        if (abbrev->tag == DW_TAG_subprogram
> >           || abbrev->tag == DW_TAG_variable
> >           || abbrev->tag == DW_TAG_namespace
> > +          || abbrev->tag == DW_TAG_enumeration_type
> > +          || abbrev->tag == DW_TAG_structure_type
> 
> That's a very different problem - you're at the other interesting if in
> this function.  Please show me an example of debug information which
> requires this - and see the comment above which talks about why most of
> these checks are only for buggy compilers...

It's a long story :).

In Ada, we allow nested functions. In order to be able to break inside
a nested function, using "break nested_function", we need to scan the
DIEs inside subprogram DIEs and build partial symbols for them. That's
the first local change we did. Something like: if ada and then
subprogram, then do not skip to sibling.

And next, we face something a bit out of the ordinary: We had a function
that was inlined. That caused GCC to create a nameless subprogram DIE,
with an AT_specification attribute pointing to the original procedure.
The tricky part was that there was inside that procedure a nameless
enumeration DIE that also had an AT_specification. We failed on that
second AT_specification during the lookup in the hash-table.

I hope this makes sense. I'm trying to be short as I'm busier than
I have ever been right now. Don't hesitate to let me know if I'm not,
though.  It may take a bit of time for me to answer, but I will answer.

-- 
Joel


  reply	other threads:[~2005-02-16 19:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-16  0:17 Manoj Iyer
2005-02-16  1:09 ` Daniel Jacobowitz
2005-02-16  2:18   ` Joel Brobecker
2005-02-16  3:24     ` Daniel Jacobowitz
2005-02-16 22:50       ` Joel Brobecker [this message]
2005-02-17 14:30         ` Daniel Jacobowitz
2005-02-17 17:43           ` Joel Brobecker
2005-02-17  0:38       ` Manoj Iyer
2005-02-17 14:06         ` Daniel Jacobowitz
2005-02-16 13:46   ` Manoj Iyer
2005-03-02 18:32   ` Manoj Iyer

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=20050216190824.GU1200@adacore.com \
    --to=brobecker@adacore.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=manjo@austin.ibm.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