09:49 <tester_perf> Hi. I'm on systemtap 1.6 and i have quite a few scripts that seem a bit hard to build for newer versions for 3.0. So im trying to add support for syscall.perf_event_open in 1.6. I've added corresponding entries to nd_syscalls2.stp and syscalls2.stp, however that alone does not seem to be sufficient. any thoughts on what I could try next?

12:57 <fche> does not seem sufficient how?

13:02 <tester_perf> fche: hmm I tried making the following changes -- http://pastebin.com/vNLgd7vW ; then tried rebuilding systemtap. However, the following command does not show up the arguments still.

13:02 <tester_perf> ./stap -a arm -r <path_to_kernel> -L syscall.perf_event_open

13:03 <tester_perf> are there any other changes I need to make in order for stap to be able to find syscall.perf_event_open from the tapset?

13:15 <fche> tapsets aren't compiled into systemtap; you can just add new files under $prefix/share/systemtap/tapset with that stuff

13:16 <fche> stap --vp 3 .... will tel you which tapset files stap is parsing

13:16 <fche> put a perf-event.stp one nearby those

13:17 <fche> stap --vp 3 -p 1 .... will show you the parsed content back

13:37 <tester_perf> fche: I see thanks for the tips! http://pastebin.com/HBkt1KA2 -- there is a tapset dir i put in a perf_event.stp with the content from earlier

13:37 <tester_perf> Let me try it with the -p flag

13:38 <tester_perf> hmm seems to be the same output as above actually

13:57 <fche> (-p1 dumps the parse trees)

13:57 <fche> hm, stap 1.6 -- doesn't respond as informatively to --vp3 as newer ones

13:58 <fche> say, what problems did you have running older scripts with newer stap?

13:58 <fche> tried the --compatible=1.6 flag?

14:08 <tester_perf> fche: oh I see, i did not know that there was such a flag interesting!

20:18 <irker088> systemtap: jistone systemtap.git:refs/heads/master * release-3.0-68-g6d25ab3 / runtime/linux/perf.c: _stp_perf_read: check the union type before accessing fields http://tinyurl.com/z6t4xbp