[Bug translator/1155] inline function parameters
mjw at redhat dot com
sourceware-bugzilla@sourceware.org
Tue Sep 16 15:38:00 GMT 2008
------- Additional Comments From mjw at redhat dot com 2008-09-16 15:37 -------
I believe the following new regressions under 2.6.26.3-29.fc9.x86_64 are also
caused by this:
Running /home/mark/src/systemtap/testsuite/systemtap.examples/check.exp ...
FAIL: systemtap.examples/process/sig_by_pid build
FAIL: systemtap.examples/process/sig_by_pid run
FAIL: systemtap.examples/process/sig_by_proc build
FAIL: systemtap.examples/process/sig_by_proc run
FAIL: systemtap.examples/process/sigkill build
FAIL: systemtap.examples/process/sigkill run
FAIL: systemtap.examples/process/sigmon build
FAIL: systemtap.examples/process/sigmon run
They all fail in the same way:
attempting command stap -p4 sig_by_pid.stp OUT semantic error: failed to
retrieve location attribute for local 'sig' (dieof fset: 0x4bbda9): identifier
'$sig' at /usr/local/systemtap/share/systemtap/tapse t/signal.stp:92:11 semantic
error: failed to retrieve location attribute for local 't' (dieoffset:
0x4bbd9f): identifier '$t' at :93:12 semantic error: failed to retrieve location
attribute for local 'sig' (dieoffset : 0x4bbeef): identifier '$sig' at :92:11
semantic error: failed to retrieve location attribute for local 't' (dieoffset:
0x4bbee5): identifier '$t' at :93:12 semantic error: failed to retrieve
location attribute for local 'sig' (dieoffset : 0x4bd412): identifier '$sig' at
:92:11 semantic error: failed to retrieve location attribute for local 't'
(dieoffset: 0x4bd408): identifier '$t' at :93:12 semantic error: failed to
retrieve location attribute for local 'sig' (dieoffset : 0x4bbda9): identifier
'$sig' at :92:11
specific_send_sig_info used to be a larger static function in kernel/signal.c,
but in 2.6.26 is just a simple oneliner:
static int
specific_send_sig_info(int sig, struct siginfo *info, struct task_struct *t)
{
return send_signal(sig, info, t, 0);
}
--
http://sourceware.org/bugzilla/show_bug.cgi?id=1155
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the Systemtap
mailing list