Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
To: gdb@sources.redhat.com
Subject: Re: handling of absolute source file paths (feature wish/implementation idea)
Date: Fri, 23 Jan 2004 13:02:00 -0000	[thread overview]
Message-ID: <7494-Fri23Jan2004145824+0200-eliz@elta.co.il> (raw)
In-Reply-To: <20040122201642.GA26573@nevyn.them.org> (message from Daniel Jacobowitz on Thu, 22 Jan 2004 15:16:42 -0500)

> Date: Thu, 22 Jan 2004 15:16:42 -0500
> From: Daniel Jacobowitz <drow@mvista.com>
> 
> Now what would be really nice would be a manual chapter referencing all
> of these.

Is there really a reason to describe them all in one place?  I'm not
sure.

> > BTW, wasn't there a mechanism for editing/replacing part of the source 
> > prefix added, or did that get lost?
> 
> Now that sounds like a great idea.  I can't see it in the source,
> though, and it doesn't ring a bell.

How about if we make a mode which will do that editing for us?  E.g.,
imagine that we have a file whose name is recorded in the debug info
as /a/b/c/d/e/z.c, and some search path.  Then GDB would first try the
literal /a/b/c/d/e/z.c, then, for each directory X that's mentioned
in the search path, it will try these:

   X/z.c
   X/a/b/c/d/e/z.c
   X/b/c/d/e/z.c
   X/c/d/e/z.c
   X/d/e/z.c
   X/e/z.c

How does this sound?


  reply	other threads:[~2004-01-23 13:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22 15:01 Gernot Hillier
2004-01-22 15:07 ` Daniel Jacobowitz
2004-01-22 15:39   ` Gernot Hillier
2004-01-22 18:02     ` Daniel Jacobowitz
2004-01-22 16:04   ` Paul Koning
2004-01-22 17:26 ` Eli Zaretskii
2004-01-22 17:58   ` Daniel Jacobowitz
2004-03-03 17:54     ` Baurjan Ismagulov
2004-01-22 18:45   ` Andrew Cagney
2004-01-22 20:16     ` Daniel Jacobowitz
2004-01-23 13:02       ` Eli Zaretskii [this message]
2004-01-23 20:26       ` Andrew Cagney
     [not found] <1074884800.30040.ezmlm@sources.redhat.com>
2004-01-23 21:31 ` Jim Ingham
2004-03-03 16:12   ` Baurjan Ismagulov

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=7494-Fri23Jan2004145824+0200-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    --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