|
From: bhaldas <bh...@ot...> - 2006-03-31 08:37:18
|
Hi I just heard about valgrind and i tried to check our application i found that after i call fopen in some place it gets almost 4000 errors if i exit just before fopen there are only 2 errors finally it stops counting errors because there are more than 30000 either if there are so many errors it doesnt print any description for all of them it just print a description for about 10 errors Do i miss something ? is there any way to see a description for all these errors? thanks -- View this message in context: http://www.nabble.com/to-many-errors-t1373279.html#a3685401 Sent from the Valgrind - Users forum at Nabble.com. |
|
From: Tom H. <to...@co...> - 2006-03-31 08:58:51
|
In message <368...@ta...>
bh...@ot... wrote:
> I just heard about valgrind and i tried to check our application
> i found that after i call fopen in some place it gets almost 4000 errors
> if i exit just before fopen there are only 2 errors
> finally it stops counting errors because there are more than 30000
> either if there are so many errors it doesnt print any description for all
> of them
> it just print a description for about 10 errors
That just means one (or more) of those 10 errors has occurred lots
of times - if you run with -v then it should tell you at the end how
many times each error occurred.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Bob R. <bob...@co...> - 2006-03-31 12:04:11
|
On Fri, Mar 31, 2006 at 09:58:45AM +0100, Tom Hughes wrote: > In message <368...@ta...> > bh...@ot... wrote: > > > I just heard about valgrind and i tried to check our application > > i found that after i call fopen in some place it gets almost 4000 errors > > if i exit just before fopen there are only 2 errors > > finally it stops counting errors because there are more than 30000 > > either if there are so many errors it doesnt print any description for all > > of them > > it just print a description for about 10 errors > > That just means one (or more) of those 10 errors has occurred lots > of times - if you run with -v then it should tell you at the end how > many times each error occurred. > > Tom Could this be made more explicit in the message? I've seen this on the list a few times now, so valgrind probably isn't being clear enough. Bob Rossi |