* Semantic error on probe module("foo").function("bar")
@ 2010-09-12 12:56 Christian Pössinger
2010-09-12 13:39 ` Christian Pössinger
0 siblings, 1 reply; 2+ messages in thread
From: Christian Pössinger @ 2010-09-12 12:56 UTC (permalink / raw)
To: systemtap
Hello *,
I'm quiet new to systemtap and trying to understand how everything works
out. I want to connect a probe to a kernel module (mplex-stap) and access
a function within that module.
probe module("mplex-stap").function("mplex_fop_ioctl").return {...}
When I compile the module and load it (either as a out of tree module, or
throuth CONFIG_SAMPLES with the kernel build system) the module loads just
fine, but calling STAP always results in:
semantic error: missing i386 kernel/module debuginfo under
'/lib/modules/2.6.32.9-lttng-0.198/build' while resolving probe point
module("mplex-stap").function("mplex_fop_ioctl").return
Working with probes that tap into syscall.* work like a charm. Am I
missing something in my build system for my own module?
Best Regards,
Christian
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Semantic error on probe module("foo").function("bar")
2010-09-12 12:56 Semantic error on probe module("foo").function("bar") Christian Pössinger
@ 2010-09-12 13:39 ` Christian Pössinger
0 siblings, 0 replies; 2+ messages in thread
From: Christian Pössinger @ 2010-09-12 13:39 UTC (permalink / raw)
To: systemtap
After a small discussion on IRC I found the cause of my problem.
My module registers as a character device driver with the name
"mplex-stap". But the module will be displayed as "mplex_stap" on lsmod.
After changing my proble line from:
probe module("mplex-stap").function("mplex_fop_ioctl").return {...}
to
probe module("mplex_stap").function("mplex_fop_ioctl").return {...}
everything worked out.
Best Regards,
Christian
On So, 12.09.2010, 14:56, Christian Pössinger sagte:
> Hello *,
>
> I'm quiet new to systemtap and trying to understand how everything works
> out. I want to connect a probe to a kernel module (mplex-stap) and access
> a function within that module.
>
> probe module("mplex-stap").function("mplex_fop_ioctl").return {...}
>
> When I compile the module and load it (either as a out of tree module, or
> throuth CONFIG_SAMPLES with the kernel build system) the module loads just
> fine, but calling STAP always results in:
>
> semantic error: missing i386 kernel/module debuginfo under
> '/lib/modules/2.6.32.9-lttng-0.198/build' while resolving probe point
> module("mplex-stap").function("mplex_fop_ioctl").return
>
> Working with probes that tap into syscall.* work like a charm. Am I
> missing something in my build system for my own module?
>
> Best Regards,
> Christian
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-09-12 13:39 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-09-12 12:56 Semantic error on probe module("foo").function("bar") Christian Pössinger
2010-09-12 13:39 ` Christian Pössinger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).