From: Pierre Muller <muller@ics.u-strasbg.fr>
To: Felix Lee <bdgle@tigerfood.org>, gdb@sources.redhat.com
Subject: Re: remapping absolute source paths
Date: Thu, 03 Oct 2002 01:07:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20021003095556.01f4c900@ics.u-strasbg.fr> (raw)
In-Reply-To: <200210030636.g936aOi31950@paper-wolf-solo.tigerfood.org>
At 08:36 03/10/2002 , Felix Lee a écrit:
>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"
Did you try to use
dir /p/..
because it might be that gdb
does try
/p/../a/x/foo.c
normally this should be
expanded back into /a/x/foo.c
but we could probably easily get GDB to handle
it the other way around so that it gets translated into
/p/x/foo.c.
This would of course require some documentation
about this new feature, but as dir /p/..
is probably quite useless for now,
it could be adapted for this purpose,
without the need of a new gdb command.
Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
next prev parent reply other threads:[~2002-10-03 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 23:37 Felix Lee
2002-10-03 1:07 ` Pierre Muller [this message]
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=4.2.0.58.20021003095556.01f4c900@ics.u-strasbg.fr \
--to=muller@ics.u-strasbg.fr \
--cc=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