ISHIKAWA, Chiaki wrote:
So the problem is in the interface between XPCOM and JavaScript. Or that the routine on the other side of XPCOM forgets to return a valid value and instead leaves uninitialized memory in the data passed to the interface. Ugh, really hard bug to debug :-(
I agree, this sounds like the most likely reason.
If anyone has a good idea how to debug this further BEYOND this XPCOM interface, I will appreciate it very much. [This is why I wanted to know WHAT JS file, what line, etc., the JavaScript interpreter is calling, etc. Maybe this time, we need to learn WHAT SERVICE is invoked using XPCOM interface?
Normally I would suggest calling DumpJSStack() but that goes to Thunderbird's output, not gdb's, so you would need to have a way of capturing that.
-- Warning: May contain traces of nuts. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
