From: Andrew Cagney <cagney@redhat.com>
To: Stan Cox <scox@redhat.com>
Cc: frysk@sourceware.org
Subject: /an/absolute/path/program.debug; Was: [SCM] master: Add -sysroot option to fhpd.
Date: Mon, 14 Jan 2008 16:50:00 -0000 [thread overview]
Message-ID: <478B9246.3060505@redhat.com> (raw)
In-Reply-To: <20080114051518.31275.qmail@sourceware.org>
scox@sourceware.org wrote:
> +/**
> + * Given: a mock generated /sys/root/dir/usr/bin/program
> + * /sys/root/dir/usr/lib/debug/usr/bin/program.debug
> + * Elfutils can be given an absolute or relative path to look for program.debug.
> + * It will look in:
> + * 1. /sys/root/dir/usr/bin/program.debug
> + * 2. /sys/root/dir/usr/bin/a/relative/path/program.debug
> + * 3. /an/absolute/path/sys/root/dir/usr/bin/program.debug
>
I'm not sure I follow this one.
> + * It would be helpful if it also looked in /an/absolute/path/program.debug
> + * so it could be given /sys/root/dir/usr/lib/debug/usr/bin. Lacking that we
> + * need to generate a relative path that has the same effect.
>
The sysroot, by defining the top-level of the debug-info tree, provides
a consistent root for locating both:
-> the debug info
-> the source code
directory search paths are different, so, I think, would want to be
manipulated using a separate command; and their interaction with sysroot
would need to be carefully considered. For instance, given $SYSROOT,
should it search $SYSROOT/$DEBUGPATH?
> + * XXX: Change to use java.io.File?
>
Yes, definitely.
Andrew
next prev parent reply other threads:[~2008-01-14 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080114051518.31275.qmail@sourceware.org>
2008-01-14 9:06 ` Mark Wielaard
2008-01-14 13:17 ` Stan Cox
2008-01-14 16:50 ` Andrew Cagney [this message]
2008-01-14 20:27 ` /an/absolute/path/program.debug; Was: " Stan Cox
2008-01-14 17:09 ` Andrew Cagney
2008-01-14 20:33 ` Stan Cox
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=478B9246.3060505@redhat.com \
--to=cagney@redhat.com \
--cc=frysk@sourceware.org \
--cc=scox@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).