From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: handling of absolute source file paths (feature wish/implementation idea)
Date: Fri, 23 Jan 2004 20:26:00 -0000 [thread overview]
Message-ID: <4011836A.2030603@gnu.org> (raw)
In-Reply-To: <20040122201642.GA26573@nevyn.them.org>
> Hmm, maybe, but most places that I can think of would want either
> solib, or source, but not both. --with-sysroot just sets solib, also.
> I have no idea what it ought to do with debug...
If it is ment to act like chroot, then it should. That way it is at
least simple and consistent - it replaces the top-level root. People
can then refine the behavior using other path commands.
> Now what would be really nice would be a manual chapter referencing all
> of these.
>
>
>> (although an immediate source-absolute-prefix shouldn't hurt).
>>
>> BTW, wasn't there a mechanism for editing/replacing part of the source
>> prefix added, or did that get lost?
>
>
> Now that sounds like a great idea. I can't see it in the source,
> though, and it doesn't ring a bell.
Here is a starter: pathmap semantics issues
http://sources.redhat.com/ml/gdb-patches/2000-11/msg00319.html
there doesn't appear to be a patch?
Andrew
next prev parent reply other threads:[~2004-01-23 20:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 15:01 Gernot Hillier
2004-01-22 15:07 ` Daniel Jacobowitz
2004-01-22 15:39 ` Gernot Hillier
2004-01-22 18:02 ` Daniel Jacobowitz
2004-01-22 16:04 ` Paul Koning
2004-01-22 17:26 ` Eli Zaretskii
2004-01-22 17:58 ` Daniel Jacobowitz
2004-03-03 17:54 ` Baurjan Ismagulov
2004-01-22 18:45 ` Andrew Cagney
2004-01-22 20:16 ` Daniel Jacobowitz
2004-01-23 13:02 ` Eli Zaretskii
2004-01-23 20:26 ` Andrew Cagney [this message]
[not found] <1074884800.30040.ezmlm@sources.redhat.com>
2004-01-23 21:31 ` Jim Ingham
2004-03-03 16:12 ` Baurjan Ismagulov
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=4011836A.2030603@gnu.org \
--to=cagney@gnu.org \
--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