|
From: Dan K. <da...@ke...> - 2009-10-17 00:33:37
|
It's a fact of life with valgrind that you will see memory leaks from system libraries... you just have to suppress them and move on. If you're ambitious, you can make sure the upstream project knows about the leak. You might want to check for ready-made suppression files from other users. For instance, http://src.chromium.org/viewvc/chrome/trunk/src/tools/valgrind/suppressions.txt?revision=15913&pathrev=15913 might suppress some of those Fontconfig leaks you're seeing; download it and pass it to valgrind with --suppressions=suppressions.txt . The leaks that show up in the wxwindows demo can probably be ignored, too. The --generate-suppressions=all flag is helpful there; you can then copy those suppressions from the log into your suppressions file. - Dan |