This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Unknown symbol error using stap in RHEL 5.4
- From: Josh Stone <jistone at redhat dot com>
- To: Maynard Johnson <maynardj at us dot ibm dot com>
- Cc: systemtap at sourceware dot org
- Date: Wed, 12 May 2010 17:45:51 -0700
- Subject: Re: Unknown symbol error using stap in RHEL 5.4
- References: <4BEB3032.8030907@us.ibm.com>
On 05/12/2010 03:48 PM, Maynard Johnson wrote:
> This looked suspiciously like the problem reported in
> https://bugzilla.redhat.com/show_bug.cgi?id=499677. But I tried
> 'rmmod uprobes', "make -C /usr/share/systemtap/runtime/uprobes
> clean", and "rm -rf ~/.systemtap", but was not able to clear the
> problem. I noted that the systemtap level was 1.1-3, which is
> different from a fresh RHEL 5.4 install. So I tried uninstalling
> systemtap and installing the 0.9.7-5 rpm from the install DVD, but
> that didn't clear the error either. As a sanity check, I did a fresh
> install of RHEL 5.4 on another system, and was able to use stapitrace
> with no problem there.
>
> Any thoughts on what might be causing this problem?
Can you search the filesystem to make sure there's not any other version
of uprobes hanging around somewhere?
>> If the above is your problem, then I think the best recourse is to
>> rebuild the kernel without uprobes, so that SystemTap's version will get
>> used.
> Jim, thanks for your reply, but this is not really an option for users.
What Jim describes would only be the case if the user was already
compiling a custom kernel with uprobes in it. The RHEL 5.4 kernel does
not have uprobes itself.
What is the kernel version on the problem system?
Josh