|
From: Alison Z. <ali...@au...> - 2005-01-12 01:08:42
|
Hi Dennis, I have checked the errors shown, most of them are errors from library which i can do nothing. I remember when i run valgrind before, it did show me lots lots of errors. Why dose not it show me all the errors even if i added error-limit=no? Any other way to make it show all the errors? Cheers Alison Dennis Lubert wrote: > At 23:41 11.01.2005, Alison Zhang wrote: > >> Hi, >> I am trying to check memory leak problem of my C program in linux. >> And here is the result >> >> ==11795== More than 30000 total errors detected. I'm not reporting >> any more. >> ==11795== Final error counts will be inaccurate. Go fix your program! >> ==11795== Rerun with --error-limit=no to disable this cutoff. Note >> ==11795== that errors may occur in your program without prior warning >> from >> ==11795== Valgrind, because errors are no longer being displayed. >> ==11795== >> ==11795== FATAL: M_PROCMAP_BUF is too small; increase it and recompile >> >> Then the program just exited here. >> Could someone please tell me how to fix this problem. > > > First fix all the errors in your program valgrind reported, then other > errors like this will mostly disappear... > > > Carpe quod tibi datum est > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |