Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sources.redhat.com, Paul Koning <pkoning@equallogic.com>
Subject: Re: Should "dir" override the full path encoded in debug info?
Date: Sat, 24 Jun 2006 07:11:00 -0000	[thread overview]
Message-ID: <20060624070842.GC22750@adacore.com> (raw)
In-Reply-To: <20060623201839.GA2920@nevyn.them.org>

> It is quite likely that what you really want is not "dir", but this:
> 
>   http://sourceware.org/ml/gdb/2006-03/msg00189.html
> 
> Hey, Paul...

Indeed, that would solve the proble entirely. I wonder how this should
be implemented... Should the command store the rewriting rule, and have
find_and_open_source() use it when trying to locate source files?

> This might be a bug, or it might not.  But generally "dir" is used only
> for files which could not be found; first try the normal location, then
> try the search path.  This is the same thing we do for shared libraries
> (which implies that the new command would be sort-of an analog for set
> solib-absolute-prefix).  Changing anything here is tricky, because of
> the case of multiple directories with files with the same name...

Indeed, same file name used more than once in a project is an issue.
Perhaps the argument I was making saying that it "works" in most cases
is backwards, and it actually "works" in my coworker's case while it's
broken for most cases. I'm not sure I would thrilled at the prospect
of fixing this, knowing how delicate this can be.

-- 
Joel


  reply	other threads:[~2006-06-24  7:08 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 [this message]
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
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=20060624070842.GC22750@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb@sources.redhat.com \
    --cc=pkoning@equallogic.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