From: Wenji Huang <wenji.huang@oracle.com>
To: sourceware-bugzilla@sourceware.org
Cc: systemtap@sources.redhat.com
Subject: Re: [Bug runtime/6562] New: $SYSTEMTAP_DEBUGINFO_PATH does not work
Date: Tue, 27 May 2008 19:26:00 -0000 [thread overview]
Message-ID: <483BD0F1.20608@oracle.com> (raw)
In-Reply-To: <20080526073449.6562.prasad@linux.vnet.ibm.com>
prasad at linux dot vnet dot ibm dot com wrote:
[...]
> [root@prasadkr_t60p systemtap]# env | grep DEBUG
> SYSTEMTAP_DEBUGINFO_PATH=/home/prasadkr/tryvmlinux/
> [root@prasadkr_t60p systemtap]# ls -lh /home/prasadkr/tryvmlinux/
> total 72M
The debuginfo_path is a little weird. If we specify it begins with "/",
such as "/home/prasadkr/tryvmlinux/", the real searching path will be
"/home/prasadkr/tryvmlinux/lib/modules/xxx/vmlinux".
And the relative path will begin with /lib/modules/xxx/, like "build"
So you can make some addition under "tyrvmlinux" and take another test.
I suggest that debugpath.exp should be strengthened to cover the
self-built kernel case.
diff --git a/testsuite/systemtap.base/debugpath.exp
b/testsuite/systemtap.base/debugpath.exp
index b0b1220..b6e5674 100644
--- a/testsuite/systemtap.base/debugpath.exp
+++ b/testsuite/systemtap.base/debugpath.exp
@@ -10,7 +10,7 @@ expect {
wait
set test "debugpath-good"
-spawn env SYSTEMTAP_DEBUGINFO_PATH=:/usr/lib/debug stap -e "probe
kernel.function(\"sys_open\") {}" -p2
+spawn env SYSTEMTAP_DEBUGINFO_PATH=:/usr/lib/debug:build stap -e "probe
kernel.function(\"sys_open\") {}" -p2
expect {
-re {kernel.function.*pc=} { pass $test }
timeout { fail "$test (timeout2)" }
next prev parent reply other threads:[~2008-05-27 9:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 1:34 prasad at linux dot vnet dot ibm dot com
2008-05-27 19:26 ` Wenji Huang [this message]
2008-05-27 19:31 ` [Bug runtime/6562] " wenji dot huang at oracle dot com
2008-05-27 19:41 ` prasad at linux dot vnet dot ibm dot com
2008-05-28 16:57 ` srinivasa at in dot ibm dot com
2008-05-28 17:20 ` fche at redhat dot com
2008-05-28 17:24 ` ananth at in dot ibm dot com
2008-05-29 12:17 ` srinivasa at in dot ibm dot com
2008-05-29 12:23 ` ananth at in dot ibm dot com
2008-06-03 23:41 ` fche at redhat dot com
2008-07-10 16:49 ` fche at redhat dot com
2008-07-11 3:23 ` wenji dot huang at oracle dot com
2008-07-11 10:47 ` srinivasa at in dot ibm dot com
2008-10-20 15:15 ` fche at redhat dot com
2008-10-20 18:59 ` mjw at redhat dot com
2008-10-21 6:33 ` srinivasa at in dot ibm dot com
2009-02-03 5:36 ` srikar at linux dot vnet dot ibm dot com
2009-02-03 6:08 ` srikar at linux dot vnet dot ibm 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=483BD0F1.20608@oracle.com \
--to=wenji.huang@oracle.com \
--cc=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).