This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: gdb bug or corrupt dwarf info?
- From: Tom Tromey <tromey at redhat dot com>
- To: "Elmenthaler\, Jens" <JENS dot ELMENTHALER at advantest dot com>
- Cc: "gdb\ at sourceware dot org" <gdb at sourceware dot org>
- Date: Tue, 23 Apr 2013 12:08:30 -0600
- Subject: Re: gdb bug or corrupt dwarf info?
- References: <CEA8125BCE884349929B204B961E547128E06D8F at DEBOSVPEX001 dot ent dot rt dot verigy dot net> <87ip4bb6d1 dot fsf at fleche dot redhat dot com> <CEA8125BCE884349929B204B961E547128E2D92E at DEBOSVPEX001 dot ent dot rt dot verigy dot net>
>>>>> "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