Comment #1 on issue 2625 by [email protected]: Re-Throwing an error that
has a stack trace from Error.captureStack does not show correct stack trace
http://code.google.com/p/v8/issues/detail?id=2625
Weird. The exact same code in d8 works (replacing console.log() by
print()). The output is
Error
at thrower (test.js:18:13)
at wrap (test.js:21:7)
at catchIt (test.js:25:9)
at test.js:31:5
test.js:28: Error: Foo
throw e;
^
Error
at thrower (test.js:18:13)
at wrap (test.js:21:7)
at catchIt (test.js:25:9)
at test.js:31:5
The console.log output is correct in both Chrome's JS console and d8. The
difference is the output for uncaught exceptions. d8 does it correctly,
Chrome's JS console does not.
d8 uses v8::TryCatch::StackTrace() to get the stack trace of the uncaught
pending exception. Maybe Chrome is doing something different?
--
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/groups/opt_out.
