public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Stan Cox <scox@redhat.com>
To: Ray Ruvinskiy <rruvinsk@sybase.com>
Cc: frysk@sourceware.org
Subject: Re: Specifying a debuginfo path independently of sysroot
Date: Mon, 16 Jun 2008 13:20:00 -0000	[thread overview]
Message-ID: <1213622028.18458.135.camel@multics.rdu.redhat.com> (raw)
In-Reply-To: <C891E0B4-7418-4AE9-AC6B-EE5076FC51A0@sybase.com>


On Fri, 2008-06-13 at 17:13 -0400, Ray Ruvinskiy wrote:
> "/usr/lib/debug"

The reason for /usr/lib/debug is that is the standard root location for
debug information on Linux: for
example /usr/lib/debug/bin, /usr/lib/debug/usr/bin.  So the theory is
that sysroot is imitating the standard linux behavior.  Frysk "always"
has a sysroot, with the default sysroot location being "/".  Specifying
a different sysroot just tells frysk to look for the standard Linux
debugging information in a sysroot whose root is somewhere other than
"/"  For example here is the sysroot which is used to run the Frysk
sysroot tests:

frysk-core/frysk/pkglibdir/test-sysroot/usr/bin:
./  ../  funit-quicksort*

frysk-core/frysk/pkglibdir/test-sysroot/usr/lib:
./  ../  debug/  libbubble.so*

frysk-core/frysk/pkglibdir/test-sysroot/usr/lib/debug/usr/bin:
./  ../  funit-quicksort.debug*

frysk-core/frysk/pkglibdir/test-sysroot/usr/lib/debug/usr/lib:
./  ../  funit-bubblesort.debug*

frysk-core/frysk/pkglibdir/test-sysroot/usr/src/debug:
./  ../  funit-bubblesort.c  funit-quicksort.c


  reply	other threads:[~2008-06-16 13:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13 14:12 Ray Ruvinskiy
2008-06-13 15:07 ` Sami Wagiaalla
2008-06-13 15:56   ` Ray Ruvinskiy
2008-06-13 21:14     ` Rick Moseley
2008-06-16 12:22       ` Ray Ruvinskiy
2008-06-16 13:20         ` Stan Cox [this message]
2008-06-18 13:27         ` Rick Moseley

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=1213622028.18458.135.camel@multics.rdu.redhat.com \
    --to=scox@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=rruvinsk@sybase.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).