[Bug translator/16019] limit number of similar semantic errors output

["jlebon at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=16019

Jonathan Lebon <jlebon at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #9 from Jonathan Lebon <jlebon at redhat dot com> ---
Hi Siarhei,

I just pushed to the main branch a final solution to this problem. Your patch
on the exception chain inspired us to improve filtering based on the whole
chain, rather than individual errors. The way it works is that error chains are
only printed if they are unique (so e.g. the bottom error could be the same as
a previous one, but if the 'backtrace' of exceptions is different, then it will
be printed).

Comparison of errors is done based on their source (using __FUNCTION__ and
__LINE__) so that we don't even have to do any sort of fuzzy string matching.
So e.g. two error chains are the same if they have the same backtrace of
__FUNCTION__:__LINE__ for each error in the chain.

For now, we've set the cut-off at 1, meaning that only a single error chain of
each type is printed. But depending on how this works, it could be changed.

For completion, the original command mentioned in the description of this bug
report now yields the following:

$ stap -p2 -e 'probe syscall.* { next }'
semantic error: while resolving probe point: identifier 'kernel' at
/home/yyz/jlebon/codebase/systemtap/install/share/systemtap/tapset/linux/syscalls.stp:59:24
        source: probe syscall.access = kernel.function("sys_access").call
                                       ^

semantic error: missing x86_64 kernel/module debuginfo [man warning::debuginfo]
under '/lib/modules/3.11.6-200.fc19.x86_64/build'
semantic error: while resolving probe point: identifier 'syscall' at
<input>:1:7
        source: probe syscall.* { next }
                      ^

semantic error: probe point mismatch  (alternatives:  accept access acct
add_key <long list is cut off here...>) didn't find any wildcard matches:
operator '*' at :1:15
        source: probe syscall.* { next }
                              ^

Pass 2: analysis failed.  [man error::pass2]
Number of similar error messages suppressed: 137.
Rerun with -v to see them.
$

Cheers!

-- 
You are receiving this mail because:
You are the assignee for the bug.