From: Bob Rossi <bob_rossi@cox.net>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Andreas Schwab <schwab@suse.de>,
gdb@sourceware.org, gdb@sources.redhat.com,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: Should "dir" override the full path encoded in debug info?
Date: Tue, 27 Jun 2006 10:03:00 -0000 [thread overview]
Message-ID: <20060626145530.GB22589@brasko.net> (raw)
In-Reply-To: <20060626145036.GK22750@adacore.com>
On Mon, Jun 26, 2006 at 07:50:37AM -0700, Joel Brobecker wrote:
> > How about adding subcommands `add' and `remove' and having more than one
> > substitution rule?
>
> I personally think that would be overkill... Others?
Well, it seem to me that eventually users will need to subsitute
multiple paths. So, it makes sense to support it right away. I don't
know if add/remove is the best way. It would be a good idea to also
consider a key/value colon separated list. Where if they want to use :,
they will have to escape it (\).
substitute-path /home/foo=/home/bar:/home/foo\:1=/home/foo\:2
Just some ideas.
Bob Rossi
WARNING: multiple messages have this Message-ID
From: Bob Rossi <bob_rossi@cox.net>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Andreas Schwab <schwab@suse.de>,
gdb@sourceware.org, gdb@sources.redhat.com,
Eli Zaretskii <eliz@gnu.org>
Subject: Re: Should "dir" override the full path encoded in debug info?
Date: Tue, 27 Jun 2006 08:25:00 -0000 [thread overview]
Message-ID: <20060626145530.GB22589@brasko.net> (raw)
Message-ID: <20060627082500.giTPy_clvODCU7hWVPKIysYNX_O7F-hgyZdbyvszcto@z> (raw)
In-Reply-To: <20060626145036.GK22750@adacore.com>
On Mon, Jun 26, 2006 at 07:50:37AM -0700, Joel Brobecker wrote:
> > How about adding subcommands `add' and `remove' and having more than one
> > substitution rule?
>
> I personally think that would be overkill... Others?
Well, it seem to me that eventually users will need to subsitute
multiple paths. So, it makes sense to support it right away. I don't
know if add/remove is the best way. It would be a good idea to also
consider a key/value colon separated list. Where if they want to use :,
they will have to escape it (\).
substitute-path /home/foo=/home/bar:/home/foo\:1=/home/foo\:2
Just some ideas.
Bob Rossi
next prev parent reply other threads:[~2006-06-26 14:55 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
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 [this message]
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=20060626145530.GB22589@brasko.net \
--to=bob_rossi@cox.net \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=gdb@sourceware.org \
--cc=schwab@suse.de \
/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