https://codereview.chromium.org/240493007/diff/1/src/runtime.cc
File src/runtime.cc (left):
https://codereview.chromium.org/240493007/diff/1/src/runtime.cc#oldcode10933
src/runtime.cc:10933:
isolate->heap()->illegal_execution_state_string());
On 2014/04/17 10:45:51, Jakob wrote:
Turning this into a RUNTIME_ASSERT changes the error message being
thrown, but
that should never be observable from user code, right?
Yes. It should never happen. If it then indeed happens, it really
doesn't matter whether we get an "illegal exception" or "illegal
execution state".
https://codereview.chromium.org/240493007/
--
--
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.
