public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "jlebon at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/17986] unprivileged_myproc.exp and unprivileged_probes.exp regressed on el6 (systemtap-2.5-5.el6 versus release-2.6-274-gbabad5b31b70)
Date: Fri, 27 Feb 2015 15:42:00 -0000	[thread overview]
Message-ID: <bug-17986-6586-rnh5iy2pa1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17986-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17986

--- Comment #3 from Jonathan Lebon <jlebon at redhat dot com> ---
As per bug 17906, .nearest probes are now accepted for both wildcarded and
enumerated line number types. The remaining failures in unprivileged_probes.exp
seem to all be from the same error relating to process(number) probes, e.g.:

eval exec stap -p2 --privilege=stapsys -e {probe
process(10).statement(0x00000000004007f0) { println ("Hello"); exit (); }} -c
./foo
semantic error: while resolving probe point: identifier 'process' at
<input>:1:7
        source: probe process(10).statement(0x00000000004007f0) { println
("Hello"); exit (); }
                      ^

semantic error: no match

Pass 2: analysis failed.  [man error::pass2]
FAIL: unprivileged probes: --privilege=stapsys
process(number).statement(number)

-- 
You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2015-02-27 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 17:24 [Bug runtime/17986] New: " mcermak at redhat dot com
2015-02-16 20:04 ` [Bug runtime/17986] " dsmith at redhat dot com
2015-02-16 20:07 ` dsmith at redhat dot com
2015-02-19 21:27 ` jlebon at redhat dot com
2015-02-27 15:42 ` jlebon at redhat dot com [this message]
2015-04-23 15:30 ` dsmith at redhat dot com
2015-04-27 18:23 ` 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-17986-6586-rnh5iy2pa1@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).