From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/17906] New: The test to restrict nearest probes to ABSOLUTE and RELATIVE causing unprivileged_probes.exp tests with wildcards to fail
Date: Fri, 30 Jan 2015 01:55:00 -0000 [thread overview]
Message-ID: <bug-17906-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=17906
Bug ID: 17906
Summary: The test to restrict nearest probes to ABSOLUTE and
RELATIVE causing unprivileged_probes.exp tests with
wildcards to fail
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: wcohen at redhat dot com
When reviewing tests I found that a number of the tests (about 60) in
unprivileged_probes.exp were failing in:
make installcheck RUNTESTFLAGS="--debug
systemtap.unprivileged/unprivileged_probes.exp"
The tests were working in the systemtap-2.6 release. The tests are now failing
like the following expert from systemtap.log:
eval exec stap -p2 --unprivileged -e {probe
process.library("libfoo.so").statement("libfoofunc@libfoo.c:*").nearest {
println ("Hello"); exit (); }} -c ./foo
semantic error: while resolving probe point: identifier 'process' at
<input>:1:7
source: probe
process.library("libfoo.so").statement("libfoofunc@libfoo.c:*").nearest {
println ("Hello"); exit (); }
^
semantic error: .nearest is only valid with absolute or relative line numbers
Pass 2: analysis failed. [man error::pass2]
FAIL: unprivileged probes: --unprivileged
process.library(string).statement(string).nearest
A git bisect tracked the problem down to:
$ git bisect bad
2ff2868418227fcce0319020b02c9f4dc5ef6274 is the first bad commit
commit 2ff2868418227fcce0319020b02c9f4dc5ef6274
Author: Jonathan Lebon <jlebon@redhat.com>
Date: Tue Sep 2 12:00:42 2014 -0400
nearest probes: restrict to ABSOLUTE and RELATIVE
:100644 100644 eda0e3c937da791270a68daf6976362da5e248ef
fc45b76e84f556355d52c4c4027f2d978b84bd88 M tapsets.cxx
It looks like this doesn't accept wildcards and will cause them to be flagged
as errors.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2015-01-30 1:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 1:55 wcohen at redhat dot com [this message]
2015-02-05 23:05 ` [Bug translator/17906] " jlebon at redhat dot com
2015-02-27 15:40 ` jlebon 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-17906-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).