fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
sscox has joined #systemtap
wcohen has joined #systemtap
sscox has quit [Remote host closed the connection]
orivej has joined #systemtap
sscox has joined #systemtap
hpt has joined #systemtap
orivej has quit [Ping timeout: 245 seconds]
wcohen has quit [Ping timeout: 245 seconds]
wcohen has joined #systemtap
orivej has joined #systemtap
mjw has joined #systemtap
hpt has quit [Ping timeout: 245 seconds]
sscox has quit [Ping timeout: 245 seconds]
khaled has joined #systemtap
orivej has quit [Ping timeout: 272 seconds]
wcohen has quit [Ping timeout: 272 seconds]
sscox has joined #systemtap
drsmith has left #systemtap [#systemtap]
wcohen has joined #systemtap
drsmith has joined #systemtap
amerey_ has joined #systemtap
orivej has joined #systemtap
wielaard has joined #systemtap
mjw has quit [Ping timeout: 245 seconds]
orivej has quit [Ping timeout: 258 seconds]
<khaled>
Hi All, Is there a documentation link or bug number to describe why do systemtap causes a 32bit process to sigfault in uretprobes on 64bit kernels?
wielaard is now known as mjw
orivej has joined #systemtap
<fche>
khaled, that sounds a little bit familiar
<fche>
have you tried running the equivalent perf probe against that same process ?
<fche>
just to factor out kernel bugs rather than systemtap buts
<khaled>
Yes and it failed until a friend of mine provided a fix that works on perf but not with systemtap