On 1/22/16 4:51 PM, Terry Stanley wrote:
Breaking on console.log: FF debugger showed single turn call stack Chrome debugger with Async selected showed deep stack Console output: FF showed deep stack (as expected) Chrome showed single turn
Seems like people are incrementally introducing this stuff or just have bugs. :(
You are correct. The extended stack trace format in MarkM's message is not enough to represent async stacks.
OK, it's not just me. All I'm saying is we should go ahead and use a format that _can_ represent them.
The full Causeway format is more than what's needed for the async stacks you are asking about.
Excellent. That reduces the problem to using a larger subset of the Causeway format, right?
The deep stack you see here follows asynchronous causality as it flows across worker boundaries.
That's pretty nifty. Being able to represent that too would be nice.
It would be great to have browser support for such stitching together of intra-vat (page/worker) and cross-worker causality. Do the Causeway object formats <http://wiki.erights.org/wiki/Causeway_Platform_Developer> for representing these look like an interesting start?
I haven't had a chance to study them in detail, but at first glance yes. -Boris _______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
