This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/16019] limit number of similar semantic errors output
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Sat, 12 Oct 2013 14:52:30 +0000
- Subject: [Bug translator/16019] limit number of similar semantic errors output
- Auto-submitted: auto-generated
- References: <bug-16019-6586 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16019
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
--- Comment #2 from Frank Ch. Eigler <fche at redhat dot com> ---
An interesting approach (suppressing throw semantic_error's if
likely duplicate), but probably not quite right. For example,
single systemwide static counters don't do justice if e.g.
there are more than one --remote=FOO compile jobs being done
in sequence. Also, avoiding throwing an exception in the
duplicate case could lead to problems if control flow progresses
past an error state.
We were thinking of addressing duplication far downstream,
at the point where errors are eventually printed, within
systemtap_session::print_error. The trick there is that
we'd necessarily need to be fuzzy with matching for duplicates
(as the semantic_error msg's have custom text embedded already).
So some way of marking up these semantic_errors for similarity-
grouping is needed. This could be using fuzzy matching at the
string level, or subclassing / explicit-tagging-in-new-fields
of the semantic_error classes themselves.
--
You are receiving this mail because:
You are the assignee for the bug.