fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
derek0883 has quit [Remote host closed the connection]
khaled has quit [Quit: Konversation terminated!]
khaled has joined #systemtap
khaled has quit [Quit: Konversation terminated!]
derek0883 has joined #systemtap
hpt has joined #systemtap
zodbot has quit [Remote host closed the connection]
zodbot has joined #systemtap
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
orivej has quit [Ping timeout: 240 seconds]
derek0883 has quit [Remote host closed the connection]
derek0883 has joined #systemtap
_whitelogger has joined #systemtap
derek0883 has quit [Remote host closed the connection]
khaled has joined #systemtap
hpt has quit [Ping timeout: 260 seconds]
hpt has joined #systemtap
hpt has quit [Ping timeout: 256 seconds]
orivej has joined #systemtap
khaled has quit [Remote host closed the connection]
khaled has joined #systemtap
khaled has quit [Remote host closed the connection]
khaled has joined #systemtap
lzap has joined #systemtap
<lzap>
hello, I am trying a trivial example on F33 (syscall.open) and I am getting weird error
<lzap>
unresolved target-symbol expression: identifier '$filename' at int-access.stp:7:28
<lzap>
source: filename = user_string($filename);
tromey has joined #systemtap
<lzap>
It's just literally "print a filiename that is being opened"
<fche>
can you fpaste your whole script ?
<fche>
it could be simply that $filename is not defined at that point
<fche>
right, so use the filename variable, already packaged for you
<fche>
not user_string($filename)
<lzap>
oooh
<lzap>
that's new!
<fche>
not really
<fche>
what's new is that newer kernels make it mandatory
<lzap>
ok last time I used this on EL7 :-)
<lzap>
like 7.2ish, thanks
<fche>
because they switch syscalls through a pt_regs based switcheroo gadget, without exposing individual parms in dwarf
<fche>
so even back in rhel7, you could use the filename variable
<fche>
I bet you'll see it listed for a stap -L run there
<fche>
syscall.open filename:string mode:long __nr:long name:string flags:long flags_str:string argstr:string $filename:long int $flags:long int $mode:long int
<lzap>
yeah thanks
<lzap>
I am trying to construct a script that would show me what is spinning on my drives
<fche>
electrons :)
<lzap>
I need to know which ones, it's driving me crazy
<lzap>
please remind me how do I run tap script for all processes?
<fche>
stap is by default systemwide
khaled has quit [Quit: Konversation terminated!]
<lzap>
omg I just found I actually blogged this already, and here am I - constructing this again
<lzap>
weird I see no activity on syscall.open even when I cat a file
sscox has joined #systemtap
<lzap>
is there a list of all probes available on my system?
<fche>
try syscall.open*
<fche>
stap -L is your general list friend
<khaled>
Hi Frank, I am facing a situation where my built kernel has a dwarfless modules, Please check this paste https://paste.centos.org/view/87f3ff42
<fche>
khaled, do you know whether the gentoo build system strips modules?
<fche>
whether it saves stripped debuginfo somewhere?
<khaled>
No, they don't
<fche>
the kernel is one matter (vmlinux file), but sometimes some distros treat modules specially
<fche>
ok see if you can find the btrfs.ko file and run readelf -S /path/to/btrfs.ko
<fche>
in case gentoo does stripped kernel modules (or debugging generally) in the fedora flavour, we could try hosting those bits on our debuginfod server
<khaled>
Gentoo is a source based distro, I build my kernel myself, but there is a distro provided tool to make it easier named genkernel, I'll check what it does exactly
<fche>
aha, yeah in that case it won't help much
<fche>
(unless ... well you could save your kernel build tree
<fche>
run debuginfod -F against it
<fche>
and then systemtap can find the original .ko / vmlinux whatever files in there,