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/30841] New: [gdb, symtab] gdb-add-index doesn't support .gnu_debugaltlink Date: Tue, 12 Sep 2023 09:41:54 +0000 [thread overview] Message-ID: <bug-30841-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=30841 Bug ID: 30841 Summary: [gdb, symtab] gdb-add-index doesn't support .gnu_debugaltlink Product: gdb Version: HEAD Status: NEW Severity: enhancement Priority: P2 Component: symtab Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- Say we have an executable a.out, with a .gnu_debugaltlink to a dwz file a.dwz. Adding a .gdb_index section to a.out also requires adding a minimal .gdb_index section to a.dwz. Our current implementation of gdb-add-index, based on the "save gdb-index" command (which currently only generates a symbol-file.gdb-index) doesn't support this. Supporting this would involve: - modifying "save gdb-index" to also generate a symbol-file.dwz-gdb-index, and - modifying gdb-add-index to add that as a .gdb_section to the file pointed to by the .gnu_debugaltlink. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-09-12 9:41 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-12 9:41 vries at gcc dot gnu.org [this message] 2023-09-12 9:42 ` [Bug symtab/30841] [gdb, symtab] support .gnu_debugaltlink in gdb-add-index vries at gcc dot gnu.org 2023-09-12 15:46 ` tromey at sourceware dot org 2023-09-12 16:25 ` vries at gcc dot gnu.org 2023-09-13 3:18 ` sam at gentoo dot org 2023-09-13 6:53 ` vries at gcc dot gnu.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-30841-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).