From: Kai Schuetz <Kai.Schuetz@synopsys.com>
To: Tom Tromey <tromey@redhat.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: Crash triggered by DWARF debug info: Any ideas ?
Date: Wed, 13 Feb 2013 11:45:00 -0000 [thread overview]
Message-ID: <15151570812B8041A31A98C098B7E751042EDC@DE02WEMBX2.internal.synopsys.com> (raw)
In-Reply-To: <87liatnxmi.fsf@fleche.redhat.com>
Hi Tom,
> -----Original Message-----
> From: Tom Tromey [mailto:tromey@redhat.com]
> Sent: Tuesday, February 12, 2013 20:25
> To: Kai Schuetz
> Cc: gdb@sourceware.org
> Subject: Re: Crash triggered by DWARF debug info: Any ideas ?
>
> >>>>> "Kai" == Kai Schuetz <Kai.Schuetz@synopsys.com> writes:
>
> Kai> I'm looking into some crash in gdb 7.5.1 in the DWARF reader.
> Kai> The DWARF (v3) debug info in the case is pretty basic (it was
> Kai> generated by the "ARM Assembler", version 4.0).
> Kai> The .debug_info section just consists of a single debug info entry
> Kai> for each compilation unit, consisting of name, producer, comp_dir,
> Kai> low_pc, high_pc and stmt_list. The .debug_line section contains
> Kai> line statements for the compilation units.
> [...]
> Kai> Any idea what to hunt for ?
>
> I don't think there's an easy way to debug it. Offhand I don't know what is
> wrong. You might try having end_symtab_get_static_block always return a
> block. It's easier to do this with a newer gdb, this area changed a bit.
What is the relation of DWARF info and (static?) blocks ?
I assume there should be one static block per compilation unit ?
With "newer gdb" I assume you refer to one checked out CVS since 7.5.1 is the latest release ?
Thanks,
Kai
next prev parent reply other threads:[~2013-02-13 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 16:38 Kai Schuetz
2013-02-12 19:25 ` Tom Tromey
2013-02-13 11:45 ` Kai Schuetz [this message]
2013-02-13 17:49 ` Tom Tromey
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=15151570812B8041A31A98C098B7E751042EDC@DE02WEMBX2.internal.synopsys.com \
--to=kai.schuetz@synopsys.com \
--cc=gdb@sourceware.org \
--cc=tromey@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