public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug mi/27876] New: debuginfod-downloaded source files don't pass proper fullname across mi / (gdb)info source Date: Mon, 17 May 2021 17:48:51 +0000 [thread overview] Message-ID: <bug-27876-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27876 Bug ID: 27876 Summary: debuginfod-downloaded source files don't pass proper fullname across mi / (gdb)info source Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: mi Assignee: unassigned at sourceware dot org Reporter: fche at redhat dot com Target Milestone: --- If gdb downloads a source file via debuginfod, it works great for the command line UI's list command. However, "info source" and the MI *stopped .... fullname="/..." report keeps the original DWARF filename. An MI consumer such as VSCODE cannot use such a file name to open the source file for itself. GDB should report fullname as the one in the debuginfod client cache. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-05-17 17:48 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-17 17:48 fche at redhat dot com [this message] 2021-11-09 18:36 ` [Bug mi/27876] " amerey at redhat dot com 2022-02-15 22:47 ` trass3r at gmail dot com 2022-03-08 20:48 ` cvs-commit at gcc dot gnu.org 2022-03-08 20:51 ` amerey at redhat dot com
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-27876-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).