From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/13313] New: Can't parse SDT_V3 operand '(%rcx,%rax,8)'
Date: Tue, 18 Oct 2011 05:34:00 -0000 [thread overview]
Message-ID: <bug-13313-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=13313
Bug #: 13313
Summary: Can't parse SDT_V3 operand '(%rcx,%rax,8)'
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
AssignedTo: systemtap@sourceware.org
ReportedBy: jistone@redhat.com
Classification: Unclassified
It seems there's yet another new SDT operand in town, with systemtap.git
compiled by gcc-4.6.1-10.fc16.x86_64.
$ stap -e 'probe process("stap").mark("cache__clean") { println($arg1) }'
WARNING: Can't parse SDT_V3 operand '(%rcx,%rax,8)': identifier '$arg1' at
<input>:1:54
source: probe process("stap").mark("cache__clean") { println($arg1) }
^
semantic error: unable to find local 'arg1' near pc 0x4f6320 in <unknown>
../cache.cxx ( (alternatives: $j): identifier '$arg1' at :1:54
source: probe process("stap").mark("cache__clean") { println($arg1) }
^
Pass 2: analysis failed. Try again with another '--vp 01' option.
$ objdump -s -j .note.stapsdt stap-cache.o
stap-cache.o: file format elf64-x86-64
Contents of section .note.stapsdt:
0000 08000000 3b000000 03000000 73746170 ....;.......stap
0010 73647400 00000000 00000000 00000000 sdt.............
0020 00000000 00000000 00000000 73746170 ............stap
0030 00636163 68655f5f 67657400 38402572 .cache__get.8@%r
0040 64782038 40363838 28257262 70290000 dx 8@688(%rbp)..
0050 08000000 3a000000 03000000 73746170 ....:.......stap
0060 73647400 00000000 00000000 00000000 sdt.............
0070 00000000 00000000 00000000 73746170 ............stap
0080 00636163 68655f5f 636c6561 6e003840 .cache__clean.8@
0090 28257263 782c2572 61782c38 29000000 (%rcx,%rax,8)...
00a0 08000000 47000000 03000000 73746170 ....G.......stap
00b0 73647400 00000000 00000000 00000000 sdt.............
00c0 00000000 00000000 00000000 73746170 ............stap
00d0 00636163 68655f5f 6164645f 5f6d6f64 .cache__add__mod
00e0 756c6500 38403136 28257273 70292038 ule.8@16(%rsp) 8
00f0 40363838 28257262 78290000 08000000 @688(%rbx)......
0100 48000000 03000000 73746170 73647400 H.......stapsdt.
0110 00000000 00000000 00000000 00000000 ................
0120 00000000 00000000 73746170 00636163 ........stap.cac
0130 68655f5f 6164645f 5f736f75 72636500 he__add__source.
0140 38403734 34282572 62782920 38403131 8@744(%rbx) 8@11
0150 32282572 73702900 2(%rsp).
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-10-18 5:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 5:34 jistone at redhat dot com [this message]
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
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@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).