Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob_rossi@cox.net>
To: Paul Koning <pkoning@equallogic.com>
Cc: gdb@sources.redhat.com
Subject: Re: Source directory trees not in build location
Date: Tue, 28 Mar 2006 23:57:00 -0000	[thread overview]
Message-ID: <20060328225733.GF9767@brasko.net> (raw)
In-Reply-To: <17449.46602.392697.675583@gargle.gargle.HOWL>

On Tue, Mar 28, 2006 at 05:17:46PM -0500, Paul Koning wrote:
> We have a large source tree with many directories.  When the system is
> built that tree appears in one place in the namespace; then the build
> results are saved in "good builds" directories, one per good build up
> to whatever we can save.
> 
> The result is that source files are not where they were at build time.
> 
> GDB can handle this on a per-directory basis with the "directory"
> command, but when you have on the order of a hundred directories that
> is excessively painful.
> 
> I made a local patch to add a source path name rewriting rule.  That
> allows a substring of the source path name to be replaced by some
> different substring.  The current implementation is simplistic -- it
> allows exactly one substitution rule, and the matching is exact string
> match.  It would be possible to allow multiple rules, and probably
> also fancier mechanisms like regexps.  That wasn't necessary for our
> application.
> 
> Is this of interest to the greater GDB?
> 
>    paul
> 

Well, I'm not sure if that's necessary. Has anyone gone back to this
patch http://sourceware.org/ml/gdb-patches/2005-10/msg00092.html?

Although, your solution seems really nice too.

Bob Rossi


  parent reply	other threads:[~2006-03-28 22:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 22:57 Paul Koning
2006-03-28 23:01 ` Daniel Jacobowitz
2006-03-28 23:57 ` Bob Rossi [this message]
2006-03-29 16:16   ` Bob Rossi
2006-03-29 22:37     ` Daniel Jacobowitz
2006-03-29 22:57       ` Paul Koning

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=20060328225733.GF9767@brasko.net \
    --to=bob_rossi@cox.net \
    --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