Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paul Koning <pkoning@equallogic.com>
To: brobecker@adacore.com
Cc: gdb@sources.redhat.com
Subject: Re: Should "dir" override the full path encoded in debug info?
Date: Sun, 25 Jun 2006 18:49:00 -0000	[thread overview]
Message-ID: <17566.35019.750000.543186@gargle.gargle.HOWL> (raw)
In-Reply-To: <20060625040715.GH22750@adacore.com>

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

 >> I think that's a bug, but the fix for the bug won't make you any
 >> happier - if told to fix it, I'd probably make the compilation
 >> directory be searched first.  But don't quote me on that; I
 >> haven't looked at this code in a while (I have another bug to fix
 >> in it but it takes me so long to re-internalize how it works that
 >> I haven't done it yet).

 Joel> That's what I thought too. I don't think it's a big deal
 Joel> because our setup is probably pretty rare. I'll see about the
 Joel> new rewrite command. Any suggestion on the name of that new
 Joel> command and its syntax. Something like this?

 Joel> (gdb) rewrite-source-path old-pattern new-pattern

 Joel> Or rewrite-source-dir. It's a bit on the longer side, but can't
 Joel> find any better name. Help!

I called it "source-substitution" but "rewrite-source-path" is
clearer.  I wouldn't make it "rewrite-source-dir". At least in my
case, it's a rewrite of the entire name, so (in theory at elast) it
could rewrite the filename.  In our case that hasn't been needed but
why disallow it?

    paul


  reply	other threads:[~2006-06-25 13: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 [this message]
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
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=17566.35019.750000.543186@gargle.gargle.HOWL \
    --to=pkoning@equallogic.com \
    --cc=brobecker@adacore.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