|
From: Gao, J. <JG...@se...> - 2003-12-23 20:14:02
|
Yes, there is a way. Use option --num-callers=5. -----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. |
|
From: Pablo A. <pal...@ne...> - 2003-12-26 04:11:09
|
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. > |
|
From: Nicholas N. <nj...@ca...> - 2004-01-04 17:57:46
|
On Tue, 23 Dec 2003, Pablo Alvarez 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).
Try the following (untested) patch, combined with a high value for
--num-callers.
N
RCS file: /home/kde/valgrind/coregrind/vg_errcontext.c,v
retrieving revision 1.48
diff -u -3 -p -r1.48 vg_errcontext.c
--- coregrind/vg_errcontext.c 4 Jan 2004 16:43:19 -0000 1.48
+++ coregrind/vg_errcontext.c 4 Jan 2004 17:56:21 -0000
@@ -290,7 +290,7 @@ void VG_(maybe_record_error) ( ThreadId
Error* p;
Error* p_prev;
UInt extra_size;
- VgRes exe_res = Vg_MedRes;
+ VgRes exe_res = Vg_HighRes;
static Bool stopping_message = False;
static Bool slowdown_message = False;
static Int vg_n_errs_shown = 0;
|