|
From: Bart V. A. <bar...@gm...> - 2009-07-07 18:12:41
|
On Tue, Jul 7, 2009 at 12:15 AM, Stefan Kost<en...@ho...> wrote: > GStreamer is heavily multithreaded too and uses both mutexes and glibs > atomic operations. The unit tests are already using valgrind's memcheck > in a 2nd run. I've tried drd and helgrind once, but got a lot of > warnings and had no idea where to start. One possible approach is to start with the first reported warning and to analyze the involved call stacks carefully in order to find out why the warning was reported. Subsequently you can either insert an annotation in the source code of the analyzed program or fix the reported issue if it is a bug. Next, recompile your program and rerun it under Valgrind, and again analyze the first reported warning. After a few steps all warnings will be suppressed. This approach has already been applied succesfully to other open source projects. Bart. |