RE: [Valgrind-users] "commoned up errors"

[Pablo A. <pal...@ne...>]

Thanks for the suggestion!

At 03:13 PM 12/23/2003 -0500, Gao, Jiafu wrote:
>Yes, there is a way. Use option --num-callers=5.

I have tried using that option, but as far as I can tell that does not 
change the way errors are commoned up. Rather, it gives you a lot more 
information on the call chain for the first error, but I am getting a 
report, for example, about 2000 errors coming from a method that I know is 
only called once...

So what I really would like to know is whether someone has tried to hack 
the code to change how errors are commoned up (or to disable this feature 
completely).



>-----Original Message-----
>From: Henry Katz [mailto:hk...@st...]
>Sent: Tuesday, December 23, 2003 3:04 PM
>To: val...@li...
>Cc: pal...@ne...
>Subject: [Valgrind-users] "commoned up errors"
>
>Hello,
>
>In the code I am debugging many warnings/errors  are  nested  deep  in 
>library  function calls.
>However in Valgrind  ... " errors are commoned up using only the top three 
>function locations (the place in the current function, and that of its two 
>immediate callers)."
>So as the result  I get too many warnings/errors  bunched together 
>-  even  though  they  tend to come  from many different  code paths.
>Is there a way to change "top three function locations"   to a larger 
>number, like 5-6 or even more.
>Thank you very much for your help
>
>-henry
>
>------------------------------------------------------- This SF.net email 
>is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just 
>sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn 
>everything from the bash shell to sys admin. Click now! 
>http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click 
>_______________________________________________ Valgrind-users mailing 
>list Val...@li... 
>https://lists.sourceforge.net/lists/listinfo/valgrind-users
>
>
>
>This message (including any attachments) contains confidential information 
>intended for a specific individual and purpose, and is protected by law. 
>If you are not the intended recipient, you should delete this message. Any 
>disclosure, copying, or distribution of this message, or the taking of any 
>action based on it, is strictly prohibited.
>