From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/15671] systemtap (rpm version) can't find debuginfo for @var() use
Date: Tue, 25 Jun 2013 15:54:00 -0000 [thread overview]
Message-ID: <bug-15671-6586-7aiE4Wut2U@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15671-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15671
Josh Stone <jistone at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jistone at redhat dot com
--- Comment #7 from Josh Stone <jistone at redhat dot com> ---
FWIW, agentzh's patch for PR11096 reworks @var a fair bit, and the example here
works just fine.
But I've also determined that $var can show the issue, and this is also only a
problem in the mark("pass5*"), not mark("pass[12346]*").
$ ./run-stap -e 'probe process.mark("pass4*") { println($$name, $s->verbose) }'
-c /usr/bin/stap -p4
/home/jistone/.systemtap/cache/e0/stap_e0bc68b472d4982509234edc9c5ee57e_1907.ko
$ ./run-stap -e 'probe process.mark("pass5*") { println($$name, $s->verbose) }'
-c /usr/bin/stap -p4
semantic error: target-symbol requires debuginfo: identifier '$s' at
<input>:1:48
source: probe process.mark("pass5*") { println($$name, $s->verbose) }
^
Pass 2: analysis failed. [man error::pass2]
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-06-25 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 19:39 [Bug translator/15671] New: " dsmith at redhat dot com
2013-06-24 19:52 ` [Bug translator/15671] " mjw at redhat dot com
2013-06-24 19:58 ` dsmith at redhat dot com
2013-06-25 9:23 ` mjw at redhat dot com
2013-06-25 9:37 ` mjw at redhat dot com
2013-06-25 10:22 ` mjw at redhat dot com
2013-06-25 10:47 ` mjw at redhat dot com
2013-06-25 10:59 ` mjw at redhat dot com
2013-06-25 15:54 ` jistone at redhat dot com [this message]
2013-06-25 16:12 ` jistone at redhat dot com
2013-06-25 16:25 ` jistone at redhat dot com
2013-06-26 16:04 ` mjw 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-15671-6586-7aiE4Wut2U@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).