fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
hkshaw has joined #systemtap
hkshaw has quit [Ping timeout: 240 seconds]
lberk has quit [Ping timeout: 240 seconds]
lberk has joined #systemtap
hpt has joined #systemtap
scox_ has joined #systemtap
hpt has quit [Quit: Lost terminal]
hpt has joined #systemtap
irker217 has quit [Quit: transmission timeout]
ravi has joined #systemtap
nkambo has joined #systemtap
Humble has quit [Ping timeout: 258 seconds]
introom has joined #systemtap
<introom>
can systemtap script print out the type of a variable ?
pwithnall___ has joined #systemtap
hkshaw has joined #systemtap
hkshaw has quit [Quit: Leaving.]
bendlas has quit [Read error: Connection reset by peer]
hpt has quit [Ping timeout: 260 seconds]
bendlas has joined #systemtap
mjw has joined #systemtap
ravi has quit [Remote host closed the connection]
djellemah_ has quit [Ping timeout: 264 seconds]
djellemah_ has joined #systemtap
djellemah_ has quit [Ping timeout: 240 seconds]
djellemah_ has joined #systemtap
djellemah_ has quit [Ping timeout: 258 seconds]
djellemah_ has joined #systemtap
mbenitez has joined #systemtap
mbenitez has joined #systemtap
mbenitez has quit [Changing host]
Humble has joined #systemtap
drsmith_away is now known as drsmith
Humble has quit [Ping timeout: 260 seconds]
brolley has joined #systemtap
Humble has joined #systemtap
<fche>
hm I don't think we have a facility for that
<fche>
closest thing would be stap -L $probepoint
<fche>
^ introom
<introom>
fche: yeah. thanks.
sonal has joined #systemtap
<sonal>
i am looking for the backtrace function which could return the binary/shared obejct file from stack trace, for instance traces are :
<sonal>
dict_ref+0xc [libglusterfs.so.0.0.1]
<sonal>
0x7f17ffe25399 [fuse.so+0x8399]
<sonal>
dict_new+0x31 [libglusterfs.so.0.0.1]
<sonal>
but i want in output fuse.so,
<sonal>
generalising : i want the output to be the binary file which triggered target function
<fche>
stap backtracing is 'online' in the sense that it needs unwind data uploaded ahead of time so it has it available instantly for backtracing
<fche>
so you can get that level of detail if you run stap with -d /path/to/libglusterfs.so -d /path/to/fuse.so --ldd
<fche>
once you get pc addresses via ubacktrace(), you can map them to modules (executable names) with usymdata() e.g.
<sonal>
okay, thanks
sonal has quit [Ping timeout: 264 seconds]
wcohen has quit [Remote host closed the connection]
Humble has quit [Ping timeout: 260 seconds]
wcohen has joined #systemtap
wcohen has quit [Ping timeout: 264 seconds]
wcohen has joined #systemtap
mbenitez has quit [Quit: To office]
nkambo has quit [Remote host closed the connection]
pwithnall___ has quit [Ping timeout: 258 seconds]
sonal has joined #systemtap
mbenitez has joined #systemtap
mbenitez has joined #systemtap
mbenitez has quit [Changing host]
mjw has quit [Quit: Leaving]
irker253 has joined #systemtap
<irker253>
systemtap: scox systemtap.git:refs/heads/master * release-3.1-30-g438b5a4 / stapdyn/dynutil.cxx util.cxx util.h: Adapt stapdyn to the dyninst 9.3.1 library search model. http://tinyurl.com/k8n85tz