Often, we find ourselves attempting to debug JS code that causes a crash, generally by miscalling a XPCOM component that causes an assertion failure. Unfortunately, in such cases, the native stack captured gives little to no indication that can help developers find out how we reached this specific assertion. This is true both when we run code locally, on Try or when Firefox is released to users.
Could we find a way to capture the JS stack? I have the impression that it would be sufficient to modify our assertion macros to call a DumpJSStack() equivalent before actually crashing, and to attach the output to the Crash Reporter if available. Cheers, David -- David Rajchenbach-Teller, PhD Performance Team, Mozilla
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
