This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Bug runtime/6562] New: $SYSTEMTAP_DEBUGINFO_PATH does not work


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)" }



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]