This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Signal tapset issues?
- From: Ananth N Mavinakayanahalli <ananth at in dot ibm dot com>
- To: SystemTap <systemtap at sources dot redhat dot com>
- Date: Mon, 3 Mar 2008 19:47:08 +0530
- Subject: Signal tapset issues?
- Reply-to: ananth at in dot ibm dot com
Hi,
With the SystemTap snapshot of this morning running on a 2.6.25-rc3
kernel, I get:
[ananth@jataayu small_demos]$ stap -vv proc_snoop.stp
SystemTap translator/driver (version 0.6.1/0.133 built 2008-03-03)
Copyright (C) 2005-2008 Red Hat, Inc. and others
...
probe handle_signal@arch/x86/kernel/signal_32.c:526 kernel section=.text pc=0xc0404f8b
semantic error: failed to retrieve location attribute for local 'sig' (dieoffset: 0x9052f): identifier '$sig' at /usr/local/share/systemtap/tapset/signal.stp:391:11
semantic error: failed to retrieve location attribute for local 'sig' (dieoffset: 0x9052f): identifier '$sig' at /usr/local/share/systemtap/tapset/signal.stp:392:29
semantic error: failed to retrieve location attribute for local 'info' (dieoffset: 0x9052a): identifier '$info' at /usr/local/share/systemtap/tapset/signal.stp:393:13
semantic error: failed to retrieve location attribute for local 'info' (dieoffset: 0x9052a): identifier '$info' at /usr/local/share/systemtap/tapset/signal.stp:394:16
/proc/kallsyms doesn't contain an entry for handle_signal, but that
doesn't seem to be a problem as SystemTap is able to resolve the symbol.
The said function signature hasn't changed for a while either.
This test has been failing for a while during the weekly tests and
bz5151 is being used to track this, even though the bug says its
for the rpc-all-probes.stp failure, which probably means fixing this one
issue will fix more than one test failure.
Ideas?
Regards,
Ananth