public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "qqxnjvamvxwx at dyxyl dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/32658] GDB sometimes fails parsing debug information Date: Mon, 24 Feb 2025 12:28:47 +0000 [thread overview] Message-ID: <bug-32658-4717-r4Qasps1ff@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-32658-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=32658 Martin Simmons <qqxnjvamvxwx at dyxyl dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |qqxnjvamvxwx at dyxyl dot com --- Comment #3 from Martin Simmons <qqxnjvamvxwx at dyxyl dot com> --- Created attachment 15974 --> https://sourceware.org/bugzilla/attachment.cgi?id=15974&action=edit Patch to make arange parsing work with signed addresses The new DWARF indexer parses the .debug_aranges section for line number information (it looks like previously line number information was read from some other section). The problem is that the parser doesn't sign extend the addresses on 32-bit MIPS, which prevents them from matching during the lookup. It would work with addresses less than 2^31. The attached gdb-signed-aranges.patch fixes the problem with test-gdb.elf at least. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2025-02-24 12:28 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 2025-02-22 5:09 ` pixel@nobis-crew.org 2025-02-24 12:28 ` qqxnjvamvxwx at dyxyl dot com [this message] 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-r4Qasps1ff@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).