fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
<Vall> OK, systemtap-doc man pages installed, "man error::pass5" now works, having a look
<fche> righto
orivej has quit [Ping timeout: 260 seconds]
<Vall> man page was not very helpful... nothing specific about the error abovr
<Vall> *above
<Vall> anyway, just tried using filename directly in the printf, as you suggested
<Vall> it aborts right off:
<Vall> stap -e 'probe syscall.execve { printf("%d %d %s exec %s\n", pid(), ppid(), execname(), filename) }'
<Vall> ERROR: user string copy fault -14 at 0000000000439486 near identifier 'user_string_n' at /usr/share/systemtap/tapset/uconversions.stp:120:10
<Vall> trying with argstr now
<Vall> exactly the same thing happens with argstr as with the kernel_string($filename): it runs for a while, and then aborts with ERROR: user string copy fault -14 at 0000000000439486 near identifier 'user_string_n' at /usr/share/systemtap/tapset/uconversions.stp:120:10
<Vall> :-(
<Vall> Any ideas, fche?
<fche> Vall, hi, the man page (current version) says to try --suppress-handler-errors or --skip-badvars stap options
<fche> these things can happen e.g. if the syscall parameters reside in user memory that hasn't actually been paged in yet
DuncanT has quit [Ping timeout: 255 seconds]
orivej has joined #systemtap
_whitelogger has joined #systemtap
orivej has quit [Remote host closed the connection]
orivej has joined #systemtap
przemoc has quit [Ping timeout: 255 seconds]
przemoc has joined #systemtap
jistone has quit [Remote host closed the connection]
przemoc has quit [Ping timeout: 268 seconds]
jistone has joined #systemtap
przemoc has joined #systemtap
_whitelogger has joined #systemtap
orivej has joined #systemtap
przemoc has quit [Ping timeout: 260 seconds]
naveen has joined #systemtap
naveen has quit [Client Quit]
naveen has joined #systemtap
orivej has quit [Read error: Connection reset by peer]
drsmith_away is now known as drsmith
drsmith is now known as drsmith_away
<Vall> back
<Vall> fell asleep last night ;-)
<Vall> fche: thanks for the suggestion, will try.
<Vall> fche: seems like it solved the issue, my one-liner above has been running for almost half an hour and hasn't aborted yet
<Vall> will let it run a little more until I declare that fixed
gromero has joined #systemtap
<fche> righto
<fche> I believe newer systemtap has that more automated, in the sense that user-space strings that are unavailable will get the hex address substituted instead of an outright error
CME_ has joined #systemtap
CME has quit [Ping timeout: 260 seconds]
CME_ is now known as CME
groleo has joined #systemtap
groleo has left #systemtap [#systemtap]
CME has quit [Ping timeout: 258 seconds]
CME has joined #systemtap
naveen has quit [Ping timeout: 260 seconds]
naveen has joined #systemtap
naveen has quit [Client Quit]
naveen has joined #systemtap
naveen has quit [Quit: WeeChat 1.9]
groleo has joined #systemtap
groleo has left #systemtap [#systemtap]
groleo has joined #systemtap
groleo has left #systemtap [#systemtap]
Vall has quit [Ping timeout: 246 seconds]
Vall has joined #systemtap
gromero has quit [Remote host closed the connection]
Vall has quit [Ping timeout: 246 seconds]
Vall has joined #systemtap
<Vall> fche, just reporting back that I've left my one-liner running the whole day and it is working OK; I think we can now safely say that your suggestion of adding the " --suppress-handler-errors" and "--skip-badvars" options (I'm running with both) have indeed fixed the issue. Many thanks for your help!
Vall has quit [Ping timeout: 240 seconds]
<fche> righto
<fche> also see if a newer version of stap can be made available for your distro; it takes care of this particular complication automatically
DuncanT has joined #systemtap