This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: error in stap
oh yes, my fault. not sure why my automated script did not update
/boot/grub/menu.lst and so the kernel image is not in sync with the
kernel header files.
Thanks!!!
On Fri, Apr 24, 2009 at 6:49 AM, Mark Wielaard <mjw@redhat.com> wrote:
> Hi Peter,
>
> On Fri, 2009-04-24 at 06:28 -0400, Peter Teoh wrote:
>> My systemtap has git-pulled and updated as of now. ? While doing some
>> script processing, I got the following errors:
>> staprun:insert_module:47 inserting module
>> staprun:insert_module:66 module options: _stp_bufsize=0
>> Error inserting module '/tmp/stap2jIKVp/stap_9237.ko': Invalid module format
>> [...]
>> And dmesg shows:
>>
>> [ 1429.082734] stap_9237: disagrees about version of symbol module_layout
>> [ 1429.087594] stap_9237: disagrees about version of symbol module_layout
>>
>> My script is just a simple netcore analysis:
>>
>> probe kernel.function("*@net/core/dev.c").call {
>> ? printf("%s -> %s\n", thread_indent(1), probefunc());
>> ? print_backtrace();
>> ? printf("\n");
>> }
>>
>> Any ideas?
>
> That script should just work (it does for me). Although tracing the call
> chain and printing a full backtrace on each function entry is somewhat
> double.
>
> The error you are seeing looks like your running kernel (uname -r) is
> different from you kernel-devel sources (rpm -q kernel-devel - or the
> equivalent dpkg -s line) stap is finding.
>
> Cheers,
>
> Mark
>
>
>
>
--
Regards,
Peter Teoh