Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kai Schuetz <Kai.Schuetz@synopsys.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Crash triggered by DWARF debug info: Any ideas ?
Date: Fri, 08 Feb 2013 16:38:00 -0000	[thread overview]
Message-ID: <15151570812B8041A31A98C098B7E75104291D@DE02WEMBX2.internal.synopsys.com> (raw)

Hi,

I'm looking into some crash in gdb 7.5.1 in the DWARF reader.
The DWARF (v3) debug info in the case is pretty basic (it was generated by the "ARM Assembler", version 4.0).
The .debug_info section just consists of a single debug info entry for each compilation unit, consisting of name, producer, comp_dir, low_pc, high_pc and stmt_list. The .debug_line section contains line statements for the compilation units.

When symbol loading is triggered in gdb it crashes inside of record_block_range due to "block" being 0.
This is due to end_symtab_get_static_block() returning 0 when called in process_full_comp_unit().
Highpc and lowpc look reasonable at this point.

(I also tried skipping the call of dwarf2_record_block_ranges() if "static_block" is 0, however this lead to lots of warnings about psymtabs and symtabs being inconsistent (warning: (Internal error: pc 0x178 in read in psymtab, but not in symtab.)), and the source line mapping not working).

Any idea what to hunt for ?

Thanks,
Kai


             reply	other threads:[~2013-02-08 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08 16:38 Kai Schuetz [this message]
2013-02-12 19:25 ` Tom Tromey
2013-02-13 11:45   ` Kai Schuetz
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=15151570812B8041A31A98C098B7E75104291D@DE02WEMBX2.internal.synopsys.com \
    --to=kai.schuetz@synopsys.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