From: "jkenisto at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug documentation/11554] Document SYSTEMTAP_DEBUGINFO_PATH better
Date: Tue, 25 May 2010 13:36:00 -0000 [thread overview]
Message-ID: <20100524155348.17748.qmail@sourceware.org> (raw)
In-Reply-To: <20100428180723.11554.jkenisto@us.ibm.com>
------- Additional Comments From jkenisto at us dot ibm dot com 2010-05-24 15:53 -------
In response to another perplexed user, Srikar Dronamraju wrote:
-----
From my experience stap looks for debuginfo files in this order.
As soon as it finds a vmlinux file, it stops searching even if that
vmlinux file is not debug file.
The directory containing vmlinux can also specified by using
SYSTEMTAP_DEBUGINFO_PATH environmental variable. [How? Jim]
/boot/vmlinux-`uname -r`
/boot/.debug/vmlinux-`uname -r`
/usr/lib/debug/boot/vmlinux-`uname -r`
/boot/vmlinux-`uname -r`.debug
/boot/.debug/vmlinux-`uname -r`.debug
/usr/lib/debug/boot/`uname -r`5.1snap2.debug
/lib/modules/`uname -r`/vmlinux
/lib/modules/`uname -r`/vmlinux.debug
/lib/modules/`uname -r`/.debug/vmlinux.debug
/usr/lib/debug/lib/modules/`uname -r`/vmlinux.debug
-----
How did you determine this, Srikar?
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11554
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2010-05-24 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 21:06 [Bug documentation/11554] New: " jkenisto at us dot ibm dot com
2010-04-28 21:11 ` [Bug documentation/11554] " jistone at redhat dot com
2010-04-28 21:55 ` jkenisto at us dot ibm dot com
2010-05-25 13:36 ` jkenisto at us dot ibm dot com [this message]
2010-05-25 14:56 ` srikar at linux dot vnet dot ibm dot com
[not found] <bug-11554-1110@http.sourceware.org/bugzilla/>
2010-10-14 21:24 ` lberk at redhat dot com
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=20100524155348.17748.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.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).