Re: Signal tapset issues?

[Ananth N Mavinakayanahalli <ananth at in dot ibm dot com>]

On Mon, Mar 03, 2008 at 07:47:08PM +0530, Ananth N Mavinakayanahalli wrote:
> 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?

OK, I see bz5555 for this exact issue, but this can now be reproduced on
a 32bit x86 system too.

Ananth