This is the mail archive of the
systemtap@sources.redhat.com
mailing list for the systemtap project.
Re: Runtime probe example causes oops
- From: Hien Nguyen <hien at us dot ibm dot com>
- To: Martin Hunt <hunt at redhat dot com>
- Cc: "systemtap at sources dot redhat dot com" <systemtap at sources dot redhat dot com>, "Spirakis, Charles" <charles dot spirakis at intel dot com>
- Date: Wed, 13 Jul 2005 09:51:13 -0700
- Subject: Re: Runtime probe example causes oops
- References: <42D404BC.2060306@us.ibm.com> <1121273266.3751.15.camel@tiger>
Martin Hunt wrote:
os_timer was written by Charles. I hadn't really looked at it. It
works fine on my Pentium M running RHEL4 with the latest patches. Well,
it doesn't crash but the data it collects is not right. I'm a bit
concerned that the oops shows it was in the runtime, but I cannot see
how it could have crashed at that particular point. Do you always get
the Oops? If so, could you try putting some printks in
_stp_symbol_sprint() in sym.c? The Oops says
_stp_symbol_print() called kallsyms_lookup() and that is where it
crashed.
Martin
I also tried the other probes under the probes directory and had same
results. I am going to do what you suggest to figure out what is going on.
Thanks, Hien.