This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Symbol resolution problem in stap on FC5
- From: srinivasa <srinivasa at in dot ibm dot com>
- To: systemtap at sources dot redhat dot com
- Date: Tue, 25 Apr 2006 22:43:56 +0530
- Subject: Symbol resolution problem in stap on FC5
- Organization: IBM
Hi
I have installed systemtap(systemtap-20060422) along with elfutils
patch(elfutils-0.120.tar.gz,elfutils-portability.patch) on FC5. But when
I wrote a simple script to probe sys_open(),sys_open didn't get probed.
So I retained temprory files and checked it.
============================================
probe kernel.statement("sys_open") {
printf("hi\n");
}
==============================================
Found that in stap_9697.c address to be probed is not valid.
=====================================================
static struct kprobe dwarf_kprobe_probe_0[1]= {
{.addr= (void *) 0xc0151313} <<<<this adress to be probed>>>
};
char const * dwarf_kprobe_probe_0_location_names[1] = {
"kernel.function(\"sys_open@fs/open.c:1089\")"
};
========================================================
[root@localhost stap]# cat /proc/kallsyms | grep sys_open
c0152074 T do_sys_open
c015211e T sys_openat
c0152139 T sys_open
=========================================
But when I specified the address explicitly it works cleraly.
=================================
probe kernel.statement(0xc0152139) {
printf("hi\n");
}
====================================
These are the kernel packages I have
===============================
rpm -qa | grep kernel
kernel-debuginfo-2.6.15-1.2054_FC5
kernel-smp-devel-2.6.15-1.2054_FC5
kernel-devel-2.6.15-1.2054_FC5
kernel-smp-2.6.15-1.2054_FC5
kernel-2.6.15-1.2054_FC5
===================================
Is my analysis is correct? or this is a bug. Please clarify.