This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
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