From: Earl Chew <earl_chew@agilent.com>
To: gdb@sources.redhat.com
Cc: Daniel Jacobowitz <drow@mvista.com>
Subject: Re: remapping absolute source paths
Date: Thu, 03 Oct 2002 10:07:00 -0000 [thread overview]
Message-ID: <3D9C7929.5D94489D@agilent.com> (raw)
In-Reply-To: <20021003143218.GA24188@nevyn.them.org>
Daniel Jacobowitz wrote:
> On Wed, Oct 02, 2002 at 11:36:23PM -0700, Felix Lee wrote:
> > 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?
>
> Actually, I think that Earl implemented #2 in the message:
> [RFC PATCH] Finding files in source trees
> in September. Earl, mind resending that for more comments? I think
> you satisfied my concerns completely.
I refer you to:
http://sources.redhat.com/ml/gdb-patches/2002-09/msg00319.html
Daniel's concerns are raised in:
http://sources.redhat.com/ml/gdb-patches/2002-09/msg00322.html
and I provided answers in:
http://sources.redhat.com/ml/gdb-patches/2002-09/msg00324.html
BTW I should point out that this patch is relative to another patch
I made to introduce openp_1() which implements openp() but allows
it to be immune to occurrences of DIRNAME_SEPARATOR which
can appear in the filenames embedded in the debugging information.
When this occurs, substitution into $cdir causes surprising
results!
This is a particular risk in Win32 environments because : can
occur in the context of filenames.
See
http://sources.redhat.com/ml/gdb-patches/2002-09/msg00317.html
for details.
Earl
prev parent reply other threads:[~2002-10-03 17: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
2002-10-03 2:01 ` Felix Lee
2002-10-03 7:31 ` Daniel Jacobowitz
2002-10-03 10:07 ` Earl Chew [this message]
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=3D9C7929.5D94489D@agilent.com \
--to=earl_chew@agilent.com \
--cc=drow@mvista.com \
--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