https://bugs.kde.org/show_bug.cgi?id=501713
--- Comment #6 from zephyrus00jp <ishik...@yk.rim.or.jp> --- BTW, please see the use of valgrind to check for bugs in Firefox. https://blog.mozilla.org/jseward/2015/02/11/mochitests-are-now-valgrind-clean/ (Admittedly, it is old and was written in 2014. But it was my understanding that some people did run firefox for checking memory errors since then.) Also, I checked the Thunderbird code by ASAN run. But ASAN can't detected uninitialized code, that is why I ran thunderbird under valgrind. Problem with thunderbird is that the size of developer community is much smaller than that of firefox and that is why there was not much input from thunderbird developer community on this particular issue. I am following the usage of valgrind with mozilla code: https://firefox-source-docs.mozilla.org/contributing/debugging/debugging_firefox_with_valgrind.html But there have been issues of running thunderbird under valgrind because not many people have run such combination. I think I need to fix this issue one way or the other to make the execution of mochitest suite of thunderbird under valgrind. Otherwise, I cannot trust the result of the test run under valgrind. Obviously, the failure to initialize return code which may have random value would invalidate the test run. Hmm... As of now, ASAN run does not show any glaring errors, but just recently, coverity static analyzer reported various uninitialized field usages and so I am very uncomfortable with the current comm-central thunderbird tree as far as the uninitialized memory issue is concerned. TIA -- You are receiving this mail because: You are watching all bug changes.
