This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
RE: Target variable that was defined by our own kernel module
David,
Do you mean I need to create a mymodule-debuginfo rpm in the
same way as for kernel-debuginfo of Linux?
Thanks,
--
John Liang
-----Original Message-----
From: systemtap-owner@sourceware.org [mailto:systemtap-owner@sourceware.org]
On Behalf Of David Smith
Sent: Tuesday, May 29, 2007 11:09 AM
To: John Liang
Cc: 'Systemtap List'
Subject: Re: Target variable that was defined by our own kernel module
John Liang wrote:
> HI There,
>
> For the following systemtap script, I run into a compiler error:
>
> probe module("mymodule").("foobar"){
> if($myparm)
> dosomething
> }
That first line should be:
probe module("mymodule").function("foobar"){
> It looks if $myparm is a data structure defined in Linux Kernel,
> It would compile and run without problem; but if it is a defined
> by my own module, then it gave me a "unresolved symbol error for
> $myparm".
>
> Any suggestions to solve this?
Make sure the debug information is installed for your kernel module.
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)