From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/10913] New: bad/misleading translator error message
Date: Fri, 06 Nov 2009 19:36:00 -0000 [thread overview]
Message-ID: <20091106193626.10913.dsmith@redhat.com> (raw)
Here's the test script:
====
function foo:long()
%{
THIS->__retvalue = 5;
}
probe begin
(
printf("%d\n", foo())
}
====
Notice that the closing brace of the embedded-C function should be '%}', not
'}'. Here's what you get when you run this script.
====
# stap -vg test.stp
parse error: expected '{'
saw: junk '??THIS->__retvalue = 5;?}??probe begin?(??printf("%d\n", foo())?}'
at junk.stp:2:1
source: %{
^
1 parse error(s).
Pass 1: parsed user script and 63 library script(s) using
83216virt/20040res/2396shr kb, in 150usr/50sys/201real ms.
Pass 1: parse failed. Try again with another '--vp 1' option.
====
The translator's error message is completely confusing. It points at the open
bracket, not at the lack of a proper closing bracket.
--
Summary: bad/misleading translator error message
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: dsmith at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10913
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-11-06 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 19:36 dsmith at redhat dot com [this message]
2009-11-06 20:12 ` [Bug translator/10913] " jistone at redhat dot com
2010-03-22 19:15 ` chwang at redhat dot com
2010-03-22 21:02 ` dsmith at redhat dot com
2010-03-23 15:58 ` chwang at redhat dot com
2010-03-30 13:11 ` 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=20091106193626.10913.dsmith@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).