Status: New
Owner: ----
New issue 3920 by [email protected]: sourceUrl for inline scripts not
used in stack traces
https://code.google.com/p/v8/issues/detail?id=3920
Version: Chrome Version 40.0.2214.111 (64-bit)
OS: linux, likely all
Architecture: x64
Notice the following output in the devtools console:
Error: inline
at inlineg (temp.html:24)
at inlinef (temp.html:29)
Error: eval
at Error (native)
at evalg (eval.js:1:27)
at evalf (file:///tmp/temp.html:13:9)
When the following file is used:
<html>
<head>
<script>
function inlineg() {
throw new Error("inline");
}
function inlinef() {
try {
inlineg();
} catch (e) {
console.info(e.stack);
}
}
window.setTimeout(inlinef, 100);
//# sourceURL=inline.js
</script>
<script>
window.eval(
"function evalg() { throw Error('eval'); }\n" +
"//# sourceURL=eval.js\n");
function evalf() {
try { evalg(); } catch (e) {
console.info(e.stack);
}
}
window.setTimeout(evalf, 200);
</script>
</head>
<body>Hi</body>
</html>
What is the expected output?
Like eval, the sourceUrl annotation should modify the stack trace.
What do you see instead?
The stack trace shows the original source location
This problem complicates deobfuscation of client-side error reports for
inlined scripts.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
