From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/15052] externalvar.exp fails with dyninst
Date: Mon, 05 Aug 2013 18:07:00 -0000 [thread overview]
Message-ID: <bug-15052-6586-0z4uVQ05py@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15052-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15052
--- Comment #2 from David Smith <dsmith at redhat dot com> ---
Here's an update on this bug.
The testcase itself has been cleaned up a bit by the following commit:
commit b5ca36bda9c8a5c83eb594ed4a29a3414038792f
Author: Josh Stone <jistone@redhat.com>
Date: Mon Jun 24 17:10:08 2013 -0700
Mark externalvar.exp as KFAIL on stapdyn, PR15052
Some of the underlying functionality has also changed. We no longer get compile
errors, instead we get the following error message:
====
# stap --runtime=dyninst -d testsuite/libexternalvar.so -d
testsuite/externalvar -c testsuite/externalvar
testsuite/systemtap.base/externalvar.stp
cmd output: semantic error: VMA-tracking is only supported by the kernel
runtime (PR15052): identifier '$libvar' at
testsuite/systemtap.base/externalvar.stp:42:27
source: printf("libvar = %d\n", $libvar);
^
Pass 2: analysis failed. [man error::pass2]
====
The underlying relocation problem is still present.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-08-05 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 20:05 [Bug dyninst/15052] New: " dsmith at redhat dot com
2013-01-23 0:42 ` [Bug dyninst/15052] " jistone at redhat dot com
2013-08-05 18:07 ` dsmith at redhat dot com [this message]
2021-01-08 20:48 ` scox 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-15052-6586-0z4uVQ05py@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).