From: "chwang at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/10877] improve probe point error reporting
Date: Mon, 02 Nov 2009 17:03:00 -0000 [thread overview]
Message-ID: <20091102170342.4799.qmail@sourceware.org> (raw)
In-Reply-To: <20091031154558.10877.fche@redhat.com>
------- Additional Comments From chwang at redhat dot com 2009-11-02 17:03 -------
(In reply to comment #0)
> Currently we store just one tok* per probe_point, instead of one
> per probe point element (the stuff around the dots). This leads
> to hard-to-interpret error messages
>
> % stap -p2 -e 'probe kernel.junkction("sdf") {}'
> semantic error: probe point mismatch at position 1 (alternatives:
> function(number) function(string) mark(string) statement(number)
> statement(string) trace(string)): identifier 'kernel' at <input>:1:7 while
> resolving probe point kernel.junkction("sdf")
> source: probe kernel.junkction("sdf") {}
> ^
> Pass 2: analysis failed. Try again with another '--vp 01' option.
>
> Instead, we should store a tok* per probe point element, so that an
> error can point the caret at just the right spot, and we can drop
> the "at position N" from the error description body.
To confirm, you are suggesting the use of:
> source: probe kernel.junkction("sdf") {}
> ^
Yes?
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10877
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-11-02 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 15:46 [Bug translator/10877] New: " fche at redhat dot com
2009-11-02 17:03 ` chwang at redhat dot com [this message]
2009-11-05 13:57 ` [Bug translator/10877] " 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=20091102170342.4799.qmail@sourceware.org \
--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).