This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: SystemTap on Fedora 11


Hi -

On Fri, Feb 13, 2009 at 06:42:56PM -0600, Maynard Johnson wrote:
> [...]
> ># /usr/local/bin/stap -ve 'probe begin {printf("hello\n"); exit()}'
> OK, running this was helpful.  It pointed at the need for "kernel-devel 
> package', which this system did have a kernel-devel package installed.  But 
> when I started to look more closely, I saw mismatches in kernel versions 
> between the running kernel and the kernel-devel package (kernel-debuginfo 
> package, too).  I *think* I have all that straightened out now.  

> Now, when I run the above command, I get further.

That should not happen, as the kernel-devel package is sought much
later than any of that script level parsing.


> [...]
> Pass 3: using cached 
> /home/ppcteam/.systemtap/cache/44/stap_4449db3bfcad42c34a15064adafe91cf_348.c
> Pass 4: using cached 
> /home/ppcteam/.systemtap/cache/44/stap_4449db3bfcad42c34a15064adafe91cf_348.ko
> Pass 5: starting run.
> Error inserting module 
> '/tmp/stapUvlh6p/stap_4449db3bfcad42c34a15064adafe91cf_348.ko': Invalid 
> module format

"dmesg" should give you more information.  Maybe that .ko was built
with a different version of kernel-devel than appropriate for the host
machine, though that shouldn't happen by accident either.  (That's
because the makefiles etc. include version strings in the pathnames.
A mismatching kernel-devel should not be touched by systemtap.)

Anyway, while we're working what happened, zap your
$HOME/.systemtap/cache directory and try again.


- FChE


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]