public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/29929] New: gdb looks for "target:" file on the target
Date: Wed, 21 Dec 2022 20:48:56 +0000	[thread overview]
Message-ID: <bug-29929-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 29929
           Summary: gdb looks for "target:" file on the target
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: remote
          Assignee: unassigned at sourceware dot org
          Reporter: tromey at sourceware dot org
  Target Milestone: ---

A simple way to reproduce this bug is to:
$ gdb /bin/ls
(gdb) target remote | gdbserver - /bin/ls
(gdb) cont

If you examine the output, you'll see something like:

Reading target:/usr/lib/debug/lib64//libcap.so.2.48-2.48-4.fc36.x86_64.debug
from remote target...

That "target:" is leaking through to the remote, which is
nonsensical.

It comes from this code in find_separate_debug_file:

          debugfile = target_prefix ? "target:" : "";
          debugfile += gdb_sysroot;
          debugfile += debugdir;

(top-gdb) p gdb_sysroot
$18 = "target:"

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

             reply	other threads:[~2022-12-21 20:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 20:48 tromey at sourceware dot org [this message]
2022-12-21 21:00 ` [Bug remote/29929] " tromey at sourceware dot org
2023-01-02 13:55 ` cvs-commit at gcc dot gnu.org
2023-01-02 13:56 ` 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-29929-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: 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).