11:48 <Amy1> serhei: "not matched" means that a probe not found in source code.

11:48 <Amy1> When this occured, stap prints that a error of "not matched".

12:49 <fche> Amy1, so if you want a stap script probe to be optional - for the script to run even if a particular probe point is not accessible, put a "?" at the end of the probe point

12:49 <fche> probe foo ? { }

13:00 <Amy1> fche: thank you

13:00 <Amy1> could I implement using stap commands?

13:00 <Amy1> I don't want to modify the script.

13:01 <fche> I don't think there is a way

13:32 <Amy1> ok, thank you

14:08 <khaled> Hi Frank, I built an rpm package for a kernel module, After installing both the package and the debug info pkg I can see the unstipped .ko file in place and the .debug files in the /lib/debug/lib/modules/<uname -r> but still stap -L module("modname").function("*") is not returning the function parameters

14:08 <khaled> Knowing that it is working for the kernel and the installed userspace binaries with debugging symbols included

14:18 <fche> khaled, you could strace stap to see where it's looking for debuginfo

14:19 <fche> (or can I interest you in debuginfod-based lookup? are you running a platform with elfutils 0.178 + ?)

14:29 <khaled> mine is elfutils-libs-0.176

14:29 <khaled> strace shows stap is able to reach the symbols

14:33 <fche> can it find your modname.debug file?

14:33 <fche> how was the .debug file and the .ko created? Is there any actual dwarf content in either?

14:36 <khaled> .debug and .ko were created with rpmbuild -ba

14:44 <khaled> And I don't have permission to share the .debug at this moment :(

14:44 <fche> ok, can you strace -eopen,openat stap .... to see whether it does find the modname.debug file

14:44 <fche> and you can also rerun stap with -vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv

14:44 <fche> or so

15:02 <khaled> OK, it's a good way to continue on this, Thanks alot Frank :)