Bug 1592430 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Given the Debugger API work in bug 1592415 and bug 1592427, the server should have all the information it needs to find the `Debugger.Frame` representing the awaiter (or awaiters!) of an async function call, and include it in a stack reported to the client.

For the most part, these should be included in the stack like any other frame, with some property that indicates that it is an awaiter, not a caller, of the next younger frame.
Revision 1 by
on 
Given the Debugger API work in bug 1592415, bug 1592427, and bug 1592431, the server should have all the information it needs to find the `Debugger.Frame` representing the awaiter (or awaiters!) of an async function call, and include it in a stack reported to the client.

For the most part, these should be included in the stack like any other frame, with some property that indicates that it is an awaiter, not a caller, of the next younger frame.

Back to Bug 1592430 Comment 0