fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
wcohen has joined #systemtap
fche has quit [Remote host closed the connection]
slowfranklin_ has joined #systemtap
slowfranklin_ has quit [Client Quit]
slowfranklin has joined #systemtap
slowfranklin has quit [Quit: slowfranklin]
slowfranklin has joined #systemtap
slowfranklin has quit [Client Quit]
slowfranklin has joined #systemtap
mjw has joined #systemtap
orivej has joined #systemtap
gila has joined #systemtap
orivej has quit [Ping timeout: 250 seconds]
orivej has joined #systemtap
wcohen has quit [Ping timeout: 246 seconds]
orivej has quit [Ping timeout: 240 seconds]
wcohen has joined #systemtap
fche has joined #systemtap
CustosLimen has joined #systemtap
<CustosLimen>
hi
<fche>
what's Up?
<CustosLimen>
this should print every process that starts right: stap -ve 'probe process.begin { printf("%6d %6d %s\n", pid(), ppid(), cmdline_str()); }' /
<CustosLimen>
ah it works now
<fche>
great, what was wrong?
<CustosLimen>
fche, think it was missing debug symbols
<fche>
yeah, that hits many (but not all!) scripts
<fche>
e.g. probe syscall.execve may tell you almost as much, without debuginfo
<CustosLimen>
I'm trying to find processes that return with non zero code