public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "maxim.yegorushkin at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17934] New: substitute-source does not work for relative source filenames
Date: Fri, 06 Feb 2015 18:32:00 -0000	[thread overview]
Message-ID: <bug-17934-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 17934
           Summary: substitute-source does not work for relative source
                    filenames
           Product: gdb
           Version: 7.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: maxim.yegorushkin at gmail dot com

substitute-path does not get applied for some reason. The paths in the debug
info start with src/ which I would like to replace with /apps/maxim/s2bx/:

    17      in src/fix/main.cpp
    (gdb) show substitute-path 
    List of all source path substitution rules:
      `src' -> `/apps/maxim/s2bx'.
    (gdb) l main
    17      in src/fix/main.cpp

    (gdb) directory 
    Reinitialize source path to empty? (y or n) y
    Source directories searched: $cdir:$cwd
    (gdb) l main
    17      src/fix/main.cpp: No such file or directory.

    maxim@uklpadeci21:~ $ ls -l /apps/maxim/s2bx/fix/main.cpp
    -rw-r--r-- 1 maxim maxim 2529 Jan 30 10:25 /apps/maxim/s2bx/fix/main.cpp

Why does it not replace src/ with /apps/maxim/s2bx/ please?

I check strace of gdb and it does not even try to stat/open anything from
/apps/maxim/s2bx/.

Maxim

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


             reply	other threads:[~2015-02-06 18:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 18:32 maxim.yegorushkin at gmail dot com [this message]
2024-03-28  5:09 ` [Bug gdb/17934] " sam at gentoo 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-17934-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).