From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/15866] New: on rawhide, the 'signal.pending' and 'signal.pending.return' probe aliases are broken
Date: Tue, 20 Aug 2013 19:54:00 -0000 [thread overview]
Message-ID: <bug-15866-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=15866
Bug ID: 15866
Summary: on rawhide, the 'signal.pending' and
'signal.pending.return' probe aliases are broken
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: dsmith at redhat dot com
On rawhide (3.11.0-0.rc3.git1.1.fc20.x86_64), the 'signal.pending' and
'signal.pending.return' probe aliases are broken
====
# stap -p4 -e 'probe signal.pending { printf("%p, %d\n", sigset_add,
sigset_size) }'
semantic error: not accessible at this address [man error::dwarf]
(0xffffffff8108f56b, dieoffset: 0x9e2cf7): identifier '$set' at
/usr/local/share/systemtap/tapset/linux/signal.stp:606:16
source: sigset_add=$set
^
semantic error: not accessible at this address [man error::dwarf]
(0xffffffff8108f56b, dieoffset: 0x9e2cee): identifier '$sigsetsize' at :607:17
source: sigset_size=$sigsetsize
^
Pass 2: analysis failed. [man error::pass2]
# stap -p4 -e 'probe signal.pending.return {}'
WARNING: cannot probe .return of 1 inlined functions do_sigpending
semantic error: while resolving probe point: identifier 'kernel' at
/usr/local/share/systemtap/tapset/linux/signal.stp:615:31
source: probe signal.pending.return =
kernel.function("do_sigpending").return
^
semantic error: no match (similar functions: do_sigpending, SyS_sigpending,
sys_sigpending, SYSC_sigpending, init_sigpending)
semantic error: while resolving probe point: identifier 'signal' at <input>:1:7
source: probe signal.pending.return {}
^
semantic error: no match
Pass 2: analysis failed. [man error::pass2]
====
Both errors happen because the kernel function 'do_sigpending' is always
inlined on this rawhide kernel, which means systemtap has trouble finding its
arguments and a .return probe point doesn't exist.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2013-08-20 19:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 19:54 dsmith at redhat dot com [this message]
2013-08-20 20:00 ` [Bug tapsets/15866] " dsmith 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-15866-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).