From: "mkg at vt dot edu" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/4301] New: mark_derived_probe::join_group incomplete
Date: Fri, 30 Mar 2007 17:51:00 -0000 [thread overview]
Message-ID: <20070330185112.4301.mkg@vt.edu> (raw)
I am exploring the Myrinet 10G MX driver with SystemTap. I created two markers
called mx_ether_xmit_top and mx_ether_xmit_bottom at the top and bottom of
static function mx_ether_xmit in mx-1.2.0i/driver/linux/mx_ether.c, part of
module mx_driver.
Instead of being able to probe at the marks, there are semantic errors:
"semantic error: incomplete: keyword at <input>:1:1" with "stap -e 'probe
module("mx_driver").mark ("mx_ether_xmit_top") {exit}'". Surprisingly, there is
a different error when running "stap -e 'probe module("mx_driver").mark
("mx_ether_xmit") {exit}'": "semantic error: no match for probe point while
resolving probe point module("mx_driver").mark("mx_ether_xmit")" which is the
error I expect to see since there are no marks by that name. Thus the mark is
being found by the first command line.
The problem appears to be an incomplete implementation guarded by throwing
semantic error "incomplete" in mark_derived_probe::join_group at
tapsets.cxx:4382.
--
Summary: mark_derived_probe::join_group incomplete
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: mkg at vt dot edu
http://sourceware.org/bugzilla/show_bug.cgi?id=4301
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-03-30 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 17:51 mkg at vt dot edu [this message]
2007-03-30 18:02 ` [Bug translator/4301] " fche at redhat dot com
2007-03-30 18:28 ` mkg at vt dot edu
2007-03-30 18:44 ` fche at redhat dot com
2007-03-30 19:36 ` mkg at vt dot edu
2007-05-08 18:57 ` 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=20070330185112.4301.mkg@vt.edu \
--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).