|
From: Brian C. <cr...@fi...> - 2004-10-31 17:47:51
|
I have a problem that seems to cause valgrind some trouble. At start-up, I get through a large portion of my initialization routines, but then the program seems to stall during the reading of one particularly large datafile (which probably also causes a lot of memory allocations). If I wait long enough, eventually valgrind will eat all of the memory on the machine while reading this file, and crash. Any suggestions? |
|
From: Brian C. <cr...@fi...> - 2004-10-31 20:18:51
|
Incidentally, this seems to have been caused by my program doing lots and lots of realloc()s in small increments. Changing it to grow in larger chunks seems to workaround the problem Brian Crowder wrote: > I have a problem that seems to cause valgrind some trouble. At > start-up, I get through a large portion of my initialization routines, > but then the program seems to stall during the reading of one > particularly large datafile (which probably also causes a lot of memory > allocations). If I wait long enough, eventually valgrind will eat all > of the memory on the machine while reading this file, and crash. > > Any suggestions? > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > > > |