Comment #6 on issue 672 by bolinfest: Let the eval //@sourceURL trick work for stack traces.
http://code.google.com/p/v8/issues/detail?id=672
Is it? It appears to be a solved problem with respect to DevTools in that the sourceURL name of the buffer appears in the JS debugger in Chrome, which suggests the problem may be specific to V8 at this point. I don't know enough about the division of labor between V8, Webkit, and the rest of the browser to say definitively, though.
However, if you are saying that this should be refiled elsewhere, could you provide a link?
Or are you just restating the first comment with the link to the Chrome bug about sourceURL and DevTools that is already marked fixed?
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
