On 19 January 2015 at 10:31, Alexander E. Patrakov <patrakov at gmail.com> wrote: > 19.01.2015 05:33, Hajime Fujita wrote: [...] >> >> Also, here's how I launched valgrind. If more detailed options are >> necessary please let me know. >> $ valgrind --leak-check=yes ./src/.libs/pulseaudio ... > > > > Well, that differs from the way I tried that: > > valgrind --trace-children=yes ./src/pulseaudio > > The difference is because our intentions were different: you were focusing > on finding memory leaks, while I was searching for uninitialized variables > and use-after-free errors. And, I was trying to make sure that the > just-compiled libraries are used, and the libtool-generated bash wrapper > knows best how to do that. > > Of course, we can combine our flags, and replace --leak-check=yes with > --leak-check=full. You could also use this to make sure the libs are picked up from the build directory: libtool --mode=execute valgrind --leak-check=full --trace-children=yes ./src/pulseaudio -- Arun
