Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Joel Brobecker <brobecker@adacore.com>
Cc: 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 12:18:00 -0000	[thread overview]
Message-ID: <jefyhsaro8.fsf@sykes.suse.de> (raw)
Message-ID: <20060627121800.kscxB-Mq59wRhAYsB6oZ4IBgQscodyppI5xC5uRkFac@z> (raw)
In-Reply-To: <20060626145536.GL22750@adacore.com> (Joel Brobecker's message of 	"Mon, 26 Jun 2006 07:55:36 -0700")

Joel Brobecker <brobecker@adacore.com> writes:

> However, the idea of having
>
>         (gdb) substitute-path add from to
>         (gdb) substitute-path remove
>         (gdb) substitute-path
>
> Is interesting. The third case would print the current substitution rule.

The latter functionality should be a subcommand of show.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  parent reply	other threads:[~2006-06-26 15:00 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
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 [this message]
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=jefyhsaro8.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --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