From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/11090] New: sdt_misc.exp fails with semantic error: No cfa_ops supplied, but needed by DW_OP_call_frame_cfa
Date: Mon, 14 Dec 2009 14:02:00 -0000 [thread overview]
Message-ID: <20091214140156.11090.mjw@redhat.com> (raw)
Host: Linux springer.wildebeest.org 2.6.31.6-162.fc12.x86_64 #1 SMP Fri Dec 4 00
:06:26 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
Snapshot: version 1.0/0.143 commit release-1.0-350-g7f707e2
GCC: 4.4.2 [gcc (GCC) 4.4.2 20091027 (Red Hat 4.4.2-7)]
Distro: Fedora release 12 (Constantine)
spawn stap -c /usr/local/build/systemtap-obj/testsuite/sdt_misc-uprobe-shared.x
/usr/local/build/systemtap-obj/testsuite/sdt_misc.stp /usr/local/build/systemtap
-obj/testsuite/sdt_misc-uprobe-shared.x /usr/local/build/systemtap-obj/testsuite
/libsdt-uprobe.so
semantic error: No cfa_ops supplied, but needed by DW_OP_call_frame_cfa: identif
ier '$arg1' at /usr/local/build/systemtap-obj/testsuite/sdt_misc.stp:8:39
source: printf("In %s probe %#x\n", $$name, $arg1)
^
Pass 2: analysis failed. Try again with another '--vp 01' option.
FAIL: sdt_misc (0) shared uprobe
--
Summary: sdt_misc.exp fails with semantic error: No cfa_ops
supplied, but needed by DW_OP_call_frame_cfa
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: mjw at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=11090
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-12-14 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 14:02 mjw at redhat dot com [this message]
2010-01-13 11:51 ` [Bug translator/11090] " 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=20091214140156.11090.mjw@redhat.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).