|
From: Peter T. <pt...@li...> - 2011-11-24 09:58:48
|
Hi masters of the memory problems... I have an annoying problem, where I need some general hints. An you might know already I have been using valgrind (mostly memtool) for a long time - so the basics are ok. My current Linux-program give one valgrind error - at random - every ~0.01% of the cases. In these rare cases I see valgrind barfing with ==8110== Thread 3: ==8110== Invalid read of size 8 ==8110== at 0x4B9741C: XXEqvm (in /home/pto/tester/somelib-O.so) I know that the program has 3 threads (digging into /proc//tasks/ -> 3 dirs), and I do not have full source code for this somelib-O :/ but it seems linked to Linux-system calls to clone() I also experience - an unexpected - high memory drain in certain cases, which could relate to the same problem. Question; Can I ... or should I ... also throw "valgrind --tool=helgrind" into the game? I have not been using this yet. Any of the other tools within the valgrind family, which I should focus on? If I run valgrind --tool=massif on the same program then I normally see very modest memory usage - but should I use any special voodoo-tricks since the program is multi-threaded? (and a huge general THANX to you valgrind developers - super super work out there) /pto -- Peter Toft, PhD http://petertoft.dk |