Re: [Valgrind-users] identifying error numbers for --vgdb-error

[Philippe W. <phi...@sk...>]

On Fri, 2012-02-10 at 16:01 +0000, Rob wrote:
> >
> Thanks for the patch.  I have manually applied it to 3.7.0 (not svn) and it is a big improvement.
>   The number seems to be offset by 1 from what I would expect though, eg. --vgdb-error=5 stops after detecting 6 errors.
Thanks for the feedback. I found the reason for the off by one you have seen.
I will dig deeper in the difference between nr of errors found, and nr of errors shown.
A better patch will follow.

> One reason for printing the error number in the output would be to avoid 
> having to manually count them if there are many.  Personally I think it 
> would be nicer to always have the errors numbered to help navigating large amounts of output .

I understand this : it is effectively not very easy for the user to count the error nrs.
However, printing an error nr is changing the behaviour for all tools reporting errors.
=> changing this implies some advice/feedback from others 
Julian, Bart : an opinion ?

Philippe