On 1/20/16 10:10 AM, Mark S. Miller wrote:
I think the useful thing to do is to standardize the extended
Causeway stack trace format:
This format doesn't have an obvious way to represent "async stacks" [1],
short of hacks with the "functionName" or the "source", right?
Gecko right now represents these precisely by hacking the function name,
but that's in the context of backwards compat with existing
stack-processing tools, and a string-only stack representation. It
seems to me that moving to an object format should allow us to come up
with a cleaner way to do this.
-Boris
[1] To see what I mean, try running this in a Firefox nightly:
<!DOCTYPE HTML>
<script>
function g() {
console.log(new Error().stack);
}
function f() {
setTimeout(g, 0);
}
f();
</script>
the output you will get is:
g@filename:4:17
setTimeout handler*f@filename:7:5
@filename:9:3
As in, the stack indicates the sequence of async steps that got you to
the current source location.
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
