From: Tom Tromey <tromey@redhat.com>
To: "Elmenthaler\, Jens" <JENS.ELMENTHALER@advantest.com>
Cc: "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: gdb bug or corrupt dwarf info?
Date: Tue, 23 Apr 2013 18:08:00 -0000 [thread overview]
Message-ID: <87obd5p1b5.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CEA8125BCE884349929B204B961E547128E2D92E@DEBOSVPEX001.ent.rt.verigy.net> (Jens Elmenthaler's message of "Thu, 18 Apr 2013 11:47:18 +0000")
>>>>> "Jens" == Elmenthaler, Jens <JENS.ELMENTHALER@advantest.com> writes:
Jens> I added the following code to read_lexical_block_scope(), right
Jens> behind the processing of the children. In case the test is
Jens> positive, I "repair" the affected die_info's:
Jens> struct die_info *sibling = sibling_die(die);
Jens> if (sibling && (sibling->tag == DW_TAG_lexical_block))
Is it valid to assume that the two DIEs will be siblings?
Maybe that is the only way the bug can manifest. You may want to check.
Jens> First tests seem promising, so is there any reason I shouldn't do this?
It seems like it could work ok.
Tom
prev parent reply other threads:[~2013-04-23 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 11:40 Elmenthaler, Jens
2013-03-28 20:46 ` Tom Tromey
2013-04-18 11:47 ` Elmenthaler, Jens
2013-04-23 18:08 ` Tom Tromey [this message]
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=87obd5p1b5.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=JENS.ELMENTHALER@advantest.com \
--cc=gdb@sourceware.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