[Webkit-unassigned] [Bug 80384] New: Web Inspector: Original Call Site

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=80384

           Summary: Web Inspector: Original Call Site
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: Web Inspector
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: wycats at gmail.com
                CC: timothy at apple.com, rik at webkit.org, keishi at webkit.org,
                    pmuellr at yahoo.com, joepeck at webkit.org,
                    pfeldman at chromium.org, yurys at chromium.org,
                    bweinstein at apple.com, apavlov at chromium.org,
                    loislo at chromium.org


In browser code, it's common to create a function that will be invoked asynchronously later. Two common cases are the function passed to setTimeout and Ajax callbacks.

In these cases, it can often be convenient to be able to see the original stack trace from when the function was originally created, in addition to when it was invoked.

I would like to propose that it be possible to attach "the current call stack" to a function before it is invoked, and that when debugging code downstream from the function's invocation, that the original stack be available (probably with some kind of divider between the current stack and original stack).

I would ideally like to be able to jump back to the original stack and observe the state at that time (i.e. normal stack debugging), but if that was impossible or too difficult, just showing me the code context would be extremely helpful.

Straw man proposal:

    fn = function() { debugger; }
    fn.debugCurrentCallsite();
    setTimeout(fn, 1000);

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.