|
From: Chris P. <jud...@gm...> - 2008-08-11 02:57:33
|
Hi, I've used valgrind successfully on a number of applications running on our embedded linux system and I'm now running into problems with one particular application. It is a huge 3rd party app which for legal reasons I can't disclose much about, but I can say that I makes use of a large number of real-time threads and some kernel-to-user shared memory. When I run it under valgrind I start getting some random failures (program failures not valgrind reporting). I'm currently putting this down to the fact that valgrind supplies its own pthread implementation. I really only want to use the malloc debugging features of memcheck so at this point I'm not interested in using the thread debugging of helgrind. I found an old post http://article.gmane.org/gmane.comp.debugging.valgrind/1447/ where someone had inadvertently turned this feature off. Does anyone know a way of turning of valgrind's thread library in a controlled fashion? Is this even a good idea? Thanks, Chris |