From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org, gdb@sources.redhat.com
Cc: Joel Brobecker <brobecker@adacore.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: Should "dir" override the full path encoded in debug info?
Date: Mon, 26 Jun 2006 02:44:00 -0000 [thread overview]
Message-ID: <20060626021945.GA14880@nevyn.them.org> (raw)
In-Reply-To: <20060626020333.GA22589@brasko.net>
On Sun, Jun 25, 2006 at 10:03:34PM -0400, Bob Rossi wrote:
> On Sun, Jun 25, 2006 at 09:56:36PM -0400, Daniel Jacobowitz wrote:
> > On Sun, Jun 25, 2006 at 06:53:18PM -0700, Joel Brobecker wrote:
> > > > I think there's no need to mention `source', since `dir' doesn't,
> > > > either. So how about `subst-dir' or `alt-dir'?
> > >
> > > I'm ok with alt-dir. Any objection?
> >
> > I think it's been condensed a little too far; I'd think it was an
> > alternate to "dir", which isn't quite the case. Would substitute-dir
> > be too wordy?
>
> Please correct me if I'm wrong, but wouldn't something like
> substitute-path be more correct. I mean, this doesn't relate to a dir or
> a filename does it? I may not completly understand what the new
> functions input/output is though.
Works for me.
--
Daniel Jacobowitz
CodeSourcery
WARNING: multiple messages have this Message-ID
From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org, gdb@sources.redhat.com
Cc: Joel Brobecker <brobecker@adacore.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: Should "dir" override the full path encoded in debug info?
Date: Mon, 26 Jun 2006 03:23:00 -0000 [thread overview]
Message-ID: <20060626021945.GA14880@nevyn.them.org> (raw)
Message-ID: <20060626032300.c4J86u3TlK2tHLz2HadmS8XSoGIav-DexsD_cxzEOao@z> (raw)
In-Reply-To: <20060626020333.GA22589@brasko.net>
On Sun, Jun 25, 2006 at 10:03:34PM -0400, Bob Rossi wrote:
> On Sun, Jun 25, 2006 at 09:56:36PM -0400, Daniel Jacobowitz wrote:
> > On Sun, Jun 25, 2006 at 06:53:18PM -0700, Joel Brobecker wrote:
> > > > I think there's no need to mention `source', since `dir' doesn't,
> > > > either. So how about `subst-dir' or `alt-dir'?
> > >
> > > I'm ok with alt-dir. Any objection?
> >
> > I think it's been condensed a little too far; I'd think it was an
> > alternate to "dir", which isn't quite the case. Would substitute-dir
> > be too wordy?
>
> Please correct me if I'm wrong, but wouldn't something like
> substitute-path be more correct. I mean, this doesn't relate to a dir or
> a filename does it? I may not completly understand what the new
> functions input/output is though.
Works for me.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-26 2:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 20:18 Joel Brobecker
2006-06-23 21:51 ` Daniel Jacobowitz
2006-06-24 7:11 ` Joel Brobecker
2006-06-24 13:27 ` Paul Koning
2006-06-24 6:59 ` Eli Zaretskii
2006-06-24 7:04 ` Joel Brobecker
2006-06-24 7:08 ` Eli Zaretskii
2006-06-24 7:15 ` Joel Brobecker
2006-06-24 7:51 ` Eli Zaretskii
2006-06-24 11:19 ` Joel Brobecker
2006-06-24 13:38 ` Daniel Jacobowitz
2006-06-25 13:00 ` Joel Brobecker
2006-06-25 18:49 ` Paul Koning
2006-06-25 22:58 ` Eli Zaretskii
2006-06-26 1:56 ` Joel Brobecker
2006-06-26 2:03 ` Daniel Jacobowitz
2006-06-26 2:19 ` Bob Rossi
2006-06-26 2:44 ` Daniel Jacobowitz [this message]
2006-06-26 3:23 ` Daniel Jacobowitz
2006-06-26 3:25 ` Joel Brobecker
2006-06-26 8:38 ` Joel Brobecker
2006-06-26 12:58 ` Andreas Schwab
2006-06-26 12:38 ` Andreas Schwab
2006-06-26 15:39 ` Joel Brobecker
2006-06-26 15:54 ` Joel Brobecker
2006-06-27 10:03 ` Bob Rossi
2006-06-27 8:25 ` Bob Rossi
2006-06-28 2:26 ` Andrew STUBBS
2006-06-27 23:10 ` Andrew STUBBS
2006-06-27 12:17 ` Joel Brobecker
2006-06-27 10:06 ` Joel Brobecker
2006-06-27 18:31 ` Andreas Schwab
2006-06-27 12:18 ` Andreas Schwab
2006-06-26 10:42 ` Eli Zaretskii
2006-06-26 9:51 ` Eli Zaretskii
2006-06-24 21:31 ` Eli Zaretskii
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=20060626021945.GA14880@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=gdb@sourceware.org \
/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