This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
RE: semantic error
Yes I did ran "make install" after the build.
The output using "--vp 00004" is: http://pastebin.com/zDGPhMdu
Also, kernel crashed:
sles11sp1:/var/crash/2013-01-22-14:36 # ls -lrth
total 3.1G
-rw------- 1 root root 3.0G 2013-01-22 14:40 vmcore
-rw-r--r-- 1 root root 1.6M 2013-01-22 14:40 System.map-2.6.32.12-0.7-default
-rw-r--r-- 1 root root 187 2013-01-22 14:40 README.txt
-rw-r--r-- 1 root root 3.6M 2013-01-22 14:40 vmlinux-2.6.32.12-0.7-default.gz
-rw-r--r-- 1 root root 68M 2013-01-22 14:41 vmlinux-2.6.32.12-0.7-default.debug
Thanks,
Mehul
-----Original Message-----
From: Frank Ch. Eigler [mailto:fche@redhat.com]
Sent: Monday, January 21, 2013 9:53 PM
To: Mehul Choube
Cc: systemtap@sourceware.org
Subject: Re: semantic error
Mehul Choube <Mehul_Choube@symantec.com> writes:
> Now the command doesn't return at all:
> [...]
> sles11sp1:~/systemtap-2.0-11151/bin # time SYSTEMTAP_RUNTIME=/root/systemtap-2.0-11151/share/systemtap/runtime SYSTEMTAP_TAPSET=/root/systemtap-2.0-11151/share/systemtap/tapset ./stap -v -e 'probe vfs.read {printf("read performed\n"); exit()}'
For a hand-built stap, you should not require the
SYSTEMTAP_{RUNTIME,TAPSET} env vars at all, since those are compiled
into your ./stap binary.
> [...]
> Pass 4: compiled C into "stap_e3c44decc9b9ce95ac6db0284b62d776_1713.ko" in 3980usr/600sys/33562real ms.
> Pass 5: starting run.
> Write failed: Broken pipe
> mchoube@udesk:~$
Did you do a make-install for stap to find the staprun/stapio programs?
Add a "--vp 00004" to the stap options to gather more data. But the
initial $XDG_DATA_DIRS conflict is gone.
- FChE