Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Brendan Miller <catphive@catphive.net>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: Fwd: how to determine location of source?
Date: Tue, 03 Mar 2009 02:22:00 -0000	[thread overview]
Message-ID: <ef38762f0903021821u4b354726l602dad30e5ff3206@mail.gmail.com> (raw)
In-Reply-To: <20090303015239.GO3632@adacore.com>

No big deal. There are still parts of the manual I haven't read,
although I thought I'd checked out the stuff most relevant to my
question.

On Mon, Mar 2, 2009 at 5:52 PM, Joel Brobecker <brobecker@adacore.com> wrote:
> So, doesn't "info sources" give you the kind of info you're looking
> for. It's a little verbose, but I don't do see anything that's
> directly accessible.  Otherwise, you have "maintenance print
> psymbols PSYMS" that also gives you something you can use, but
> it's printed on a separate file, and contains even more info.

Hmm... info sources and maintenance print psymbols PSYMS gives me
relative, not absolute paths. Maybe that's all that's encoded into my
binaries by our build process, which would be cumbersome from my
purposes since I have differen't so's built in different directories.
I'm not really sure how source path encoding was handled by GCC, but
the examples in the manual made me think that absolute paths were the
norm.

Thanks,
Brendan


  reply	other threads:[~2009-03-03  2:22 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     ` Fwd: " Brendan Miller
2009-03-03  1:52       ` Joel Brobecker
2009-03-03  2:22         ` Brendan Miller [this message]
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=ef38762f0903021821u4b354726l602dad30e5ff3206@mail.gmail.com \
    --to=catphive@catphive.net \
    --cc=brobecker@adacore.com \
    --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