From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/13478] ARM tapset/signal.stp signal.handle tries to use non-existing variable $signr
Date: Wed, 07 Dec 2011 15:55:00 -0000 [thread overview]
Message-ID: <bug-13478-6586-F1oiSOl2Pl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13478-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13478
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dsmith at redhat dot com
--- Comment #1 from David Smith <dsmith at redhat dot com> 2011-12-07 15:49:57 UTC ---
Hmm, this one is quite strange.
The following code should handle that parameter being named '$sig' or '$signr':
if (@defined($sig)) {
sig = $sig
sig_name = _signal_name($sig)
}
else {
sig = $signr
sig_name = _signal_name($signr)
}
Since stap complains about not finding $signr, that means it couldn't find $sig
either.
But, one of the listed alternatives in the following error message *is* $sig:
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
I don't have access to an arm system so I can't really look at this. Could you
run the following commands and attach the output?
# stap -L 'kernel.function("handle_signal").*'
# stap -vp4 -e 'probe kernel.function("handle_signal") { print($sig) }'
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-12-07 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 15:20 [Bug tapsets/13478] New: " mjw at redhat dot com
2011-12-07 15:55 ` dsmith at redhat dot com [this message]
2011-12-07 17:40 ` [Bug tapsets/13478] " 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-F1oiSOl2Pl@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).