help needed to probe own modules

[Kai_Wong <kai_wong@symantec.com>]

I'm a new systemtap user and am trying to use it to probe my own kernel
modules. I'm successful in running sample scripts such as top.stp in
/usr/share/doc/systemtap-0.5.12 on a RHEL 5 system.

I can also do things like:
stap -e 'probe module("ext3").function("*") {printf("%d %s(%d)\n",
gettimeofday_s(), execname(), pid())}'

However, for a module, vxlogmod, that I made and added using insmod and
showed up under lsmod:
[root@srlglm1 vxlog]#lsmod
Module                  Size  Used by
 ... <snipped> ...
vxlogmod              317560  1 vxglm

stap gave the following error:
# stap -e 'probe module("vxlogmod").function("*") {}'
semantic error: no match for probe point while resolving probe point
module("vxlogmod").function("*")
Pass 2: analysis failed.  Try again with more '-v' (verbose) options.

So, my questions are:
1. Does systemtap on RHEL5 support probing kernel modules that are built and
installed separately from the distro kernel?
2. If so, what do I need to do to make it recognize my modules?

Any help will be much appreciated.
Best,
Kai
-- 
View this message in context: http://www.nabble.com/help-needed-to-probe-own-modules-tp20217654p20217654.html
Sent from the Sourceware - systemtap mailing list archive at Nabble.com.