From: Brendan Miller <catphive@catphive.net>
To: gdb@sourceware.org
Subject: Fwd: how to determine location of source?
Date: Tue, 03 Mar 2009 01:39:00 -0000 [thread overview]
Message-ID: <ef38762f0903021739i2ca4e368h2004f8a64eb01b72@mail.gmail.com> (raw)
In-Reply-To: <ef38762f0903021735v54143dd4ga38ed350616357a2@mail.gmail.com>
Er, I meant to send this to the GDB list originally so I could clarify
what I'm trying to do.
---------- Forwarded message ----------
From: Brendan Miller <catphive@catphive.net>
Date: Mon, Mar 2, 2009 at 5:35 PM
Subject: Re: how to determine location of source?
To: Joel Brobecker <brobecker@adacore.com>
On Mon, Mar 2, 2009 at 5:04 PM, Joel Brobecker <brobecker@adacore.com> wrote:
> Have a look at "set substitute-path".
Right, but before I can use that I need to know what the original path
was so I can do the substitution. My binaries come from a daily build,
and I can't know what particular path the build machine made them on
without inspecting the binaries themselves.
I did read the gdb documentation here, scroll down to the Specifying
Source Directories section:
http://sourceware.org/gdb/download/onlinedocs/gdb_8.html#SEC51
which is why I was posting on the list, because the documentation is
incomplete, or maybe I just missed something. It says that GDB
inspects the source path embeded in the binary, but I can't find where
it says how the user can do it.
next prev parent reply other threads:[~2009-03-03 1:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 0:57 Brendan Miller
2009-03-03 1:05 ` Joel Brobecker
[not found] ` <ef38762f0903021735v54143dd4ga38ed350616357a2@mail.gmail.com>
2009-03-03 1:39 ` Brendan Miller [this message]
2009-03-03 1:52 ` Fwd: " Joel Brobecker
2009-03-03 2:22 ` Brendan Miller
2009-03-03 2:39 ` Joel Brobecker
[not found] ` <ef38762f0903021927oe1429aakef0d6971ef9be5@mail.gmail.com>
2009-03-03 3:27 ` Fwd: " Brendan Miller
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=ef38762f0903021739i2ca4e368h2004f8a64eb01b72@mail.gmail.com \
--to=catphive@catphive.net \
--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