From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/13313] Can't parse SDT_V3 operand '(%rcx,%rax,8)'
Date: Tue, 15 Nov 2011 10:00:00 -0000 [thread overview]
Message-ID: <bug-13313-6586-cmgbzqA7EZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13313-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13313
Mark Wielaard <mjw at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
--- Comment #6 from Mark Wielaard <mjw at redhat dot com> 2011-11-15 09:59:44 UTC ---
(In reply to comment #5)
> commit f7719b corrects an off-by-one error in the earlier commit.
But seems to have cause the following new regressions:
Running /home/mark/src/systemtap/testsuite/systemtap.base/library.exp ...
FAIL: sdt_misc * (0 != 15)
FAIL: sdt_misc *libsdt* (0 != 15)
FAIL: sdt_misc ./libsdt.so (0 != 15)
FAIL: printf --ldd (0) (0 != 4)
spawn /usr/local/install/systemtap/bin/stap -c ./sdt_misc.x
/home/mark/src/systemtap/testsuite/systemtap.base/library.stp ./sdt_misc.x *
WARNING: Can't parse SDT_V3 operand '-4(%rbp)': identifier '$arg1' at
/home/mark/src/systemtap/testsuite/systemtap.base/library.stp:15:39
source: printf("In %s probe %#x\n", $$name, $arg1)
^
WARNING: Can't parse SDT_V3 operand '-16(%rbp)': identifier '$arg2' at :30:50
source: printf("In %s probe %#x %#x\n", $$name, $arg1, $arg2)
^
semantic error: unable to find local 'arg1' near pc 0x87d in baz
/home/mark/src/systemtap/testsuite/systemtap.base/sdt_misc.c ( (alternatives:
$i $s): identifier '$arg1' at :15: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 != 15)
Note the confusing PASS/FAIL messages that don't include the test name, I'll
fix that (commit 9ce0a9e).
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-11-15 10:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 5:34 [Bug tapsets/13313] New: " jistone at redhat dot com
2011-10-18 12:21 ` [Bug tapsets/13313] " mjw at redhat dot com
2011-10-21 16:09 ` sergiodj at redhat dot com
2011-11-11 17:03 ` fche at redhat dot com
2011-11-12 15:06 ` mjw at redhat dot com
2011-11-14 11:32 ` mjw at redhat dot com
2011-11-14 14:49 ` fche at redhat dot com
2011-11-15 10:00 ` mjw at redhat dot com [this message]
2011-11-15 10:33 ` mjw at redhat dot com
2011-12-09 12:51 ` sergiodj at redhat dot com
2011-12-09 15:09 ` fche 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-13313-6586-cmgbzqA7EZ@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).