From: "smakarov at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/14311] New: always report alternatives & positions in probe point error messages
Date: Fri, 29 Jun 2012 14:09:00 -0000 [thread overview]
Message-ID: <bug-14311-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14311
Bug #: 14311
Summary: always report alternatives & positions in probe point
error messages
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
AssignedTo: systemtap@sourceware.org
ReportedBy: smakarov@redhat.com
Classification: Unclassified
When implementing alias suffixes, it was necessary to slightly simplify the
error reporting on probe mismatch. The following currently missing information
that might be more comprehensively reported in the future:
- The position number of the mismatched component within the probe is no longer
given. (it might not be necessary to add this back now, since the exact same
information is expressed by showing the source coordinates of the mismatch
error)
- In complex situations involving both alias suffixes, the full set of
available suffixes might not be reported when there is a mismatch error.
Collecting this information accurately probably requires a much more involved
error handling scheme than what is currently used.
--
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:[~2012-06-29 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 14:09 smakarov at redhat dot com [this message]
2012-06-29 14:28 ` [Bug translator/14311] " smakarov 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-14311-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).