(2013/01/30 4:30), Gary Kwong wrote:
There should be very few warnings within the current Spidermonkey. I
suspect you may not be compiling with --enable-valgrind. This is
necessary because Spidermonkey uses a conservative garbage collector
that intentionally accesses lots of uninitialized memory, and
--enable-valgrind turns on directives to ignore these accesses.
On x86/x86_64, you'll also want to run valgrind with
--smc-check=all-non-file to avoid problems with JIT generated code.
Thus, in summary, to run Mozilla applications with Valgrind, one should use |
--track-origins=yes --enable-valgrind
--smc-check=all-non-file | when checking for uninitialized variable access.
Also, one should run it against optimized builds. Debug builds will cause quite
a bit of a slowdown.
-Gary
The last point is well taken.
I am going to create two object trees, one for debug build to get verbose
output to figure out
some logical flaws, etc., and the other for optimized build to check under
memcheck.
Thanks.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
