From: Jim Ingham <jingham@apple.com>
To: gdb@sources.redhat.com
Subject: Re: handling of absolute source file paths (feature wish/implementation idea)
Date: Fri, 23 Jan 2004 21:31:00 -0000 [thread overview]
Message-ID: <02AC0E89-4DEC-11D8-9898-000A958F4C44@apple.com> (raw)
In-Reply-To: <1074884800.30040.ezmlm@sources.redhat.com>
Klee did something similar a while back.
He added a "set pathname-substitutions" command that took a list of
pairs of path components - a "from" and a "to" element. As it went
looking for source files, if it saw the "from" element of any pair in
the full path name, it would replace it with the "to" element of that
pair, and try to open that. This command currently only edits from the
start of the path. So you could do source-absolute-prefix by giving
"/" as the from, and "/tmp/whatever" as the to. In our case, we more
often had
"/SourceMount/Projects/ProjectName" as the from, and
~releng/ReleaseName/ReleaseVersion/Projects/ProjectName as the "to".
The source changes are not that big, since we just did a straight
substitution, not any kind of regsub thingie...
Some people use this, though locally I think more folks just make links
on their local machine to make up a source tree that looks like what
the build & integration folks use on their builder machines.
Jim
On Jan 23, 2004, at 11:06 AM, gdb-digest-help@sources.redhat.com wrote:
>> (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.
>
>
--
Jim Ingham jingham@apple.com
Developer Tools
Apple Computer
next parent reply other threads:[~2004-01-23 21:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1074884800.30040.ezmlm@sources.redhat.com>
2004-01-23 21:31 ` Jim Ingham [this message]
2004-03-03 16:12 ` Baurjan Ismagulov
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
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=02AC0E89-4DEC-11D8-9898-000A958F4C44@apple.com \
--to=jingham@apple.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