public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/32658] GDB sometimes fails parsing debug information Date: Fri, 21 Feb 2025 19:16:46 +0000 [thread overview] Message-ID: <bug-32658-4717-G63ssHfNJo@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-32658-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=32658 --- Comment #1 from Tom Tromey <tromey at sourceware dot org> --- I'm not sure I can readily run this, unless you have some kind of qemu recipe I can follow. Anyway turning on complaints and -readnow says some stuff: During symbol reading: in /tmp/test-gdb.elf, DIE 0xc, DW_AT_entry_pc (0x0) outside block range (0x80010064 -> 0x80011888) During symbol reading: .debug_rnglists entry has start address of zero [in module /tmp/test-gdb.elf] During symbol reading: .debug_line address at offset 0x25d3 is 0 [in module /tmp/test-gdb.elf] During symbol reading: cannot get low and high bounds for subprogram DIE at 0x1a9d0 These are suggestive but I'm not really sure they are the bug. Reading the DWARF seems to be fine. I'd suspect maybe something with the line tables or blockvector. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2025-02-21 19:16 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-02-07 16:19 [Bug symtab/32658] New: " pixel@nobis-crew.org 2025-02-07 16:19 ` [Bug symtab/32658] " sam at gentoo dot org 2025-02-07 17:30 ` tromey at sourceware dot org 2025-02-08 11:14 ` ssbssa at sourceware dot org 2025-02-21 19:16 ` tromey at sourceware dot org [this message] 2025-02-22 5:09 ` pixel@nobis-crew.org 2025-02-24 12:28 ` qqxnjvamvxwx at dyxyl dot com 2025-03-06 18:37 ` pixel@nobis-crew.org 2025-03-07 3:47 ` sam at gentoo dot org
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=bug-32658-4717-G63ssHfNJo@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).