From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/13478] New: ARM tapset/signal.stp signal.handle tries to use non-existing variable $signr
Date: Wed, 07 Dec 2011 15:20:00 -0000 [thread overview]
Message-ID: <bug-13478-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=13478
Bug #: 13478
Summary: ARM tapset/signal.stp signal.handle tries to use
non-existing variable $signr
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
AssignedTo: systemtap@sourceware.org
ReportedBy: mjw@redhat.com
Classification: Unclassified
tapset/signal.stp signal.handle probe seems to try to use the variable $signr
for the kernel function handle_signal that isn't there on ARM:
probe signal.handle = kernel.function("handle_rt_signal64") ?,
kernel.function("handle_rt_signal32") ?,
kernel.function("handle_signal32") !,
kernel.function("handle_signal")
{
name = "handle"
if (@defined($sig)) {
sig = $sig
sig_name = _signal_name($sig)
}
else {
sig = $signr
sig_name = _signal_name($signr)
}
...
}
Running /root/systemtap/testsuite/buildok/process_test.stp
starting /root/systemtap/testsuite/buildok/process_test.stp
spawn1 stap -p4 /root/systemtap/testsuite/buildok/process_test.stp
spawn stap -p4 /root/systemtap/testsuite/buildok/process_test.stp
semantic error: unable to find local 'signr' near pc 0xc0059a54 in
handle_signal arch/arm/kernel/signal.c ( (alternatives: $regs $oldset $info $ka
$sig): identifier '$signr' at
/root/install/share/systemtap/tapset/signal.stp:606:15
semantic error: unable to find local 'signr' near pc 0xc0059a54 in
handle_signal arch/arm/kernel/signal.c ( (alternatives: $regs $oldset $info $ka
$sig): identifier '$signr' at
/root/install/share/systemtap/tapset/signal.stp:606:15
source: sig = $signr
source: sig = $signr
^
^
semantic error: unable to find local 'signr' near pc 0xc0059a54 in
handle_signal arch/arm/kernel/signal.c ( (alternatives: $regs $oldset $info $ka
$sig): identifier '$signr' at :607:33
semantic error: unable to find local 'signr' near pc 0xc0059a54 in
handle_signal arch/arm/kernel/signal.c ( (alternatives: $regs $oldset $info $ka
$sig): identifier '$signr' at :607:33
source: sig_name = _signal_name($signr)
source: sig_name = _signal_name($signr)
^
^
semantic error: unresolved type : identifier 'sig' at :606:9
semantic error: unresolved type : identifier 'sig' at :606:9
source: sig = $signr
source: sig = $signr
^
^
semantic error: unresolved type : identifier 'sig' at
/root/systemtap/testsuite/buildok/process_test.stp:43:14
semantic error: unresolved type : identifier 'sig' at
/root/systemtap/testsuite/buildok/process_test.stp:43:14
source: log(sprint(sig))
source: log(sprint(sig))
^
^
semantic error: unresolved type : identifier 'sprint' at :43:7
semantic error: unresolved type : identifier 'sprint' at :43:7
source: log(sprint(sig))
source: log(sprint(sig))
^
^
semantic error: unresolved type : identifier 'log' at :43:3
semantic error: unresolved type : identifier 'log' at :43:3
source: log(sprint(sig))
source: log(sprint(sig))
^
semantic error: unresolved type : identifier 'sig' at
/root/install/share/systemtap/tapset/signal.stp:602:9
^
semantic error: unresolved type : identifier 'sig' at
/root/install/share/systemtap/tapset/signal.stp:602:9
source: sig = $sig
source: sig = $sig
^
Pass 2: analysis failed. Try again with another '--vp 01' option.
^
Pass 2: analysis failed. Try again with another '--vp 01' option.
wait results: 32537 exp16 0 1
FAIL: buildok/process_test.stp
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-12-07 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 15:20 mjw at redhat dot com [this message]
2011-12-07 15:55 ` [Bug tapsets/13478] " dsmith at redhat dot com
2011-12-07 17:40 ` jistone at redhat dot com
2011-12-17 1:34 ` mjw at redhat dot com
2023-10-06 15:24 ` wcohen at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-13478-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).