From: Andrew Cagney <cagney@gnu.org>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: Gernot Hillier <gernot.hillier@siemens.com>, gdb@sources.redhat.com
Subject: Re: handling of absolute source file paths (feature wish/implementation idea)
Date: Thu, 22 Jan 2004 18:45:00 -0000 [thread overview]
Message-ID: <40101A49.1080902@gnu.org> (raw)
In-Reply-To: <1659-Thu22Jan2004192206+0200-eliz@elta.co.il>
> Gernot Hillier <gernot.hillier@siemens.com>
>> Date: Thu, 22 Jan 2004 16:01:14 +0100
>>
>> 3. Implement a new setting "source-absolute-prefix" (analog to the already
>> existing "solib-absolute-prefix") which allows the user to set a prefix for
>> given absolute source code paths.
>
>
> I like this suggestion the best. It does exactly what you need here:
> allow the source directory tree to be moved deeper in the hierarchy.
> Your other suggestion, searching the source path for relative file
> names, sounds like an ad-hoc hack to me.
Hmm, we're rapidly accumulating a long list of ways to alter the
absolute-prefix. cf also:
(gdb) help set debug-file-directory
Set the directory where separate debug symbols are searched for.
Separate debug symbols are first searched for in the same
directory as the binary, then in the `.debug' subdirectory,
and lastly at the path of the directory of the binary with
the global debug-file directory prepended
and the ./configure option:
--with-sysroot[=DIR] Search for usr/lib et al within DIR.
Might be time for some consolidation:
set absolute-prefix {source,solib,sysroot,debug,all} <path>
(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?
Andrew
next prev parent reply other threads:[~2004-01-22 18:45 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 [this message]
2004-01-22 20:16 ` Daniel Jacobowitz
2004-01-23 13:02 ` Eli Zaretskii
2004-01-23 20:26 ` Andrew Cagney
[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=40101A49.1080902@gnu.org \
--to=cagney@gnu.org \
--cc=eliz@elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=gernot.hillier@siemens.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