public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/25953] New: [debug-names] Support multiple per-CU indices Date: Fri, 08 May 2020 16:04:50 +0000 [thread overview] Message-ID: <bug-25953-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=25953 Bug ID: 25953 Summary: [debug-names] Support multiple per-CU indices Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- Consider the following two-file test-case: ... $ cat main.c extern void foo (void); int main (void) { foo (); return 0; } $ cat foo.c void foo (void) { } ... Compiled like this: ... $ clang-10 main.c foo.c -gdwarf-5 -gpubnames ... When running the exec with gdb, we have: ... $ gdb -batch a.out warning: Section .debug_names in /data/gdb_versions/devel/a.out length 112 does not match section length 192, ignoring .debug_names. ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-05-08 16:04 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-08 16:04 vries at gcc dot gnu.org [this message] 2020-05-08 16:07 ` [Bug symtab/25953] " vries at gcc dot gnu.org 2023-12-10 15:35 ` tromey at sourceware 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-25953-4717@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).