From: Felix Lee <bdgle@tigerfood.org>
To: gdb@sources.redhat.com
Subject: remapping absolute source paths
Date: Wed, 02 Oct 2002 23:37:00 -0000 [thread overview]
Message-ID: <200210030636.g936aOi31950@paper-wolf-solo.tigerfood.org> (raw)
Say I have a program that has some absolute path names in
the debugging info, like
/a/x/foo.c
but /a doesn't exist here. instead I have the source
in /p.
There's no easy way of making that work right in gdb, is
there? If I say "dir /p", it's not going to look for
/p/x/foo.c. If I say "dir /p/x" and for every other subdir
in the tree, then gdb will have problems picking /p/x/foo.c
from /p/y/foo.c
I'm thinking either
1. there should be a way to tell gdb that "/a" in a
source path should be remapped to "/p"
2. gdb should try every sub-path of the sourcefile name,
so it should try
/p/a/x/foo.c
/p/x/foo.c
etc.
1 is less transparent, but it's easier to control
ambiguities, like if for some reason the executable has both
/a/x/foo.c
/b/y/foo.c
which seems unlikely, but I could see it happening when
linking several libraries and packages together.
I'm leaning towards implementing 1. any thoughts?
--
next reply other threads:[~2002-10-03 6:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 23:37 Felix Lee [this message]
2002-10-03 1:07 ` Pierre Muller
2002-10-03 2:01 ` Felix Lee
2002-10-03 7:31 ` Daniel Jacobowitz
2002-10-03 10:07 ` Earl Chew
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=200210030636.g936aOi31950@paper-wolf-solo.tigerfood.org \
--to=bdgle@tigerfood.org \
--cc=gdb@sources.redhat.com \
/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