On 01/28/2013 10:08 PM, L. David Baron wrote: > On Tuesday 2013-01-29 11:04 +0900, ISHIKAWA, Chiaki wrote: >> We need to know which javascript file generated the >> uninitialized value usage to figure out the problem and fix it. >> That is, we need to find out the Context within JavaScript itself. > I don't think this is the case; there shouldn't be JavaScript code > that can lead to valgrind uninitialized memory usage warnings. The > behavior of uninitialized variables in JavaScript is well-defined. > > -David >
Yes, Javascript should not be able to trigger uninitialized memory reports with memcheck, unless it is triggering embedding code that does the uninitialized accesses. So there is little need for the capability to connect uninitialized accesses to javascript source locations. 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. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
