public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/27876] debuginfod-downloaded source files don't pass proper fullname across mi / (gdb)info source
Date: Tue, 08 Mar 2022 20:48:01 +0000	[thread overview]
Message-ID: <bug-27876-4717-I6Tvls8j10@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27876-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27876

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Aaron Merey <amerey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9ac37a9ce607b790bea17c7782d73afecaaa916c

commit 9ac37a9ce607b790bea17c7782d73afecaaa916c
Author: Aaron Merey <amerey@redhat.com>
Date:   Fri Nov 19 19:41:40 2021 -0500

    PR gdb/27876 - debuginfod-downloaded source files don't pass proper
fullname across mi / (gdb)info source

    Source files downloaded from debuginfod currently use their original DWARF
    filename as their "fullname".  This causes a mismatch between the fullname
    and the actual location of the source file in the debuginfod client cache.

    MI consumers such as VSCode will fail to open debuginfod-downloaded
    source files due to this.  Also 'info source' will fail to include the
    true paths of these files.

    To fix this, use the debuginfod cache path as the fullname for debuginfod-
    downloaded source files.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-03-08 20:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 17:48 [Bug mi/27876] New: " fche at redhat dot com
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 [this message]
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-I6Tvls8j10@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: link
Be 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).