fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
hpt has joined #systemtap
sfink has quit [Ping timeout: 272 seconds]
bchrisman has quit [Read error: Connection reset by peer]
bchrisman has joined #systemtap
sfink has joined #systemtap
nkambo has joined #systemtap
sfink has quit [Ping timeout: 260 seconds]
irker781 has quit [Quit: transmission timeout]
sfink has joined #systemtap
telnoratti has quit [Ping timeout: 240 seconds]
telnoratti has joined #systemtap
ananth has joined #systemtap
bchrisman has quit [Read error: Connection reset by peer]
bchrisman has joined #systemtap
hkshaw has joined #systemtap
naveen has joined #systemtap
srikar_away is now known as srikar
wmealing has left #systemtap [#systemtap]
nkambo has quit [Ping timeout: 240 seconds]
nkambo has joined #systemtap
jlebon has quit [Read error: Connection reset by peer]
flu has quit [Read error: Connection reset by peer]
flu has joined #systemtap
bchrisman has quit [Read error: Connection reset by peer]
bchrisman has joined #systemtap
jlebon has joined #systemtap
flu_ has joined #systemtap
jlebon_ has joined #systemtap
jistone has quit [Ping timeout: 246 seconds]
bchrisman1 has joined #systemtap
jistone has joined #systemtap
flu has quit [Ping timeout: 240 seconds]
jlebon has quit [Ping timeout: 272 seconds]
bchrisman has quit [Ping timeout: 246 seconds]
jistone has quit [Ping timeout: 256 seconds]
jistone has joined #systemtap
flu_ has quit [Ping timeout: 246 seconds]
jlebon_ has quit [Ping timeout: 265 seconds]
flu_ has joined #systemtap
jlebon has joined #systemtap
<lorddoskias>
hello, why does the probe listed here: http://pastebin.com/jFtHME9Y gives the error at the bottom of the page, given that the user_path_mountpoint_at should fire BEFORE the sys_umount probe? And also how can I check if the value stored in path[tid()] is valid ?
<lorddoskias>
okay, solved with a little bit of juggling the code around :>
<lorddoskias>
but now i get this : semantic error: unknown type in dereference: operator '->' at /usr/local/share/systemtap/tapset/linux/dentry.stp:65:33
<lorddoskias>
it seems it doesn't understand the qstr struct ;\
naveen has quit [Ping timeout: 265 seconds]
naveen has joined #systemtap
naveen1 has joined #systemtap
naveen has quit [Ping timeout: 240 seconds]
hpt has quit [Ping timeout: 260 seconds]
scox has quit [Ping timeout: 250 seconds]
ananth has quit [Quit: Leaving]
hkshaw has quit [Ping timeout: 240 seconds]
mjw has joined #systemtap
<fche>
lorddoskias, you may need a @cast()
<lorddoskias>
fche: well, i did try doing cast and also this happens in d_name in the dentry tapset, so its a problem of the core tapset library
<fche>
that's possible
<fche>
what version of stap are you using again?
<lorddoskias>
like @cast(s, "qstr" "kernel<linux/dcache.h>") to no avail
<lorddoskias>
2.9
<fche>
in your first probe, $path may not be what you think it is; in return probes, $vars are snapshotted copies of entry-time values
<fche>
that could make a difference
<lorddoskias>
well
<lorddoskias>
fche: if you are talking aobut my initial problem - i fixed that by juggling around the probes. Now the question is that I have the dentries i want to get the path they resolve to, however due to the error i'm getting from d_name i can't do that
<fche>
do you have a more recent script to look at, one that calls d_name() ?
<fche>
something's odd about the stap installation though; the d_name function has a @cast inside it, which with modern stap should sort of propagate the type information along
<fche>
but there's a type problem in your part of the script
<lorddoskias>
?
<fche>
and that is driving stap's other logic mad and giving that weird error message
<lorddoskias>
i'm all ears :)
<fche>
your printf("reading ...")
<fche>
printing %p(%s) %p(%s)
<fche>
so stap infers types dentry=int mnt=string dentry_s=int mnt_s=string
<fche>
the middle two were exchanged
<lorddoskias>
yes yes
<lorddoskias>
i just saw that
<lorddoskias>
and using your new function
<lorddoskias>
i was given correct error message and fixed that (the order of args)
<fche>
the old function works fine
scox has joined #systemtap
<lorddoskias>
but in this case shouldn't i be given an error message of wrong type?
<fche>
yes.
<lorddoskias>
rather than unknown type?
<fche>
that's the stap bug.
<lorddoskias>
yay, using stap for about 2-3 days and already found 2 bugs :d
<fche>
which was the other one?
<lorddoskias>
you already fixed it, i emailed to the mailing list and you responded, it was about givin suggestion of using -dkernel and minor docu fix to --ldd