Hi Vadym, On Wednesday 21 September 2005 20:00, Vadym Krevs wrote:
I use valgrind quite extensively and, in my experience, valgrind does not lie ...
Yes, that's what I've experienced too. This is the first time I encounter this puzzle.
If you do not believe valgrind, try some other memory debugger such as dmalloc or Intel's pin.
Well, right now with the data set I tried, the memory consumption is still acceptable (arround 40% of 1GB, the last time I check). If the machines get trashed, then I must be working on this again, otherwise, I'll just put this on my todo lists :).
Or write a small shared library overloading malloc/calloc/free and keeping a log of each memory request and preload it into your application via LD_PRELOAD.
Yes, that's basically what I've done, although I did it manually, inserting printf into the programs, after allocation and deallocation. Regards, Verdi