On Tuesday 2013-01-29 11:04 +0900, ISHIKAWA, Chiaki wrote: > I noticed many uninitialied value usage warnings from the execution of > TB under valgrind (memcheck). > > Many such usages, today, are related to JavaScript interpreter. memcheck > can print the stack trace when this condition is noticed. However, > we only get the traceback of the javascript interpreter itself in this > case. This is not very useful.
In general, as Gary said, running with --track-origins=yes can make memcheck's warnings about use of uninitialized variables much more useful. > 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 -- 𝄞 L. David Baron http://dbaron.org/ 𝄂 𝄢 Mozilla http://www.mozilla.org/ 𝄂 _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
