Comment #7 on issue 672 by [email protected]: Let the eval //@sourceURL
trick work for stack traces.
http://code.google.com/p/v8/issues/detail?id=672
For attached files the stack trace in DevTools console currently contains
the following:
Uncaught Error: hi
g :4
f stacktrace.js:11
(anonymous function) stacktrace.html:5
onclick stacktrace.html:6
even though the scripts panel shows res:/foo.js as defined by the
@SourceURL,
so the trace should show:
Uncaught Error: hi
g res:/foo.js:4
f stacktrace.js:11
(anonymous function) stacktrace.html:5
onclick stacktrace.html:6
it should also take the user to the scripts panel when (s)he clicks on
the "res:/foo.js:4"
so it isn't yet fixed, and the main reason that I added previous comment,
so that it shows up in search queries for "DevTools".
There are no other bugs elsewhere, because the assumption is that fixing it
in V8 will automatically fix it in Chromium
Attachments:
stacktrace.html 230 bytes
stacktrace.js 188 bytes
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
