public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "christian.prochaska@genode-labs.com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/24143] GDB does not read debug info file from user provided binary path if it is a symlink Date: Mon, 30 Oct 2023 12:12:02 +0000 [thread overview] Message-ID: <bug-24143-4717-b2h9e9izOl@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-24143-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=24143 --- Comment #4 from Christian Prochaska <christian.prochaska@genode-labs.com> --- 'open_and_init_dwp_file()' tries 'objfile->original_name' before 'objfile_name (objfile)', so maybe 'find_separate_debug_file_by_debuglink()' should start with 'objfile->original_name' as well? Doing that at least seems to solve the problem with the example case, but there are more places where 'objfile_name()' is used in the same file which might need to be changed as well for a proper fix. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-10-30 12:12 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-24143-4717@http.sourceware.org/bugzilla/> 2022-04-05 18:37 ` tromey at sourceware dot org 2022-04-05 19:16 ` tromey at sourceware dot org 2023-10-13 7:27 ` christian.prochaska@genode-labs.com 2023-10-14 5:10 ` sam at gentoo dot org 2023-10-30 12:12 ` christian.prochaska@genode-labs.com [this message] 2023-11-13 9:50 ` sam at gentoo dot org 2023-11-13 9:53 ` sam at gentoo dot org 2023-11-13 10:25 ` sam at gentoo dot org 2023-11-16 18:13 ` 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-24143-4717-b2h9e9izOl@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).