Updates:
Status: Fixed
Comment #15 on issue 2524 by [email protected]: Throwing an exception in
FailedAccessCheckCallback causes weird behavior.
http://code.google.com/p/v8/issues/detail?id=2524
Patch landed with r15643.
As we discussed, I'm not 100% I caught all code paths where the
access-check-failed callback could be called. So the old faulty behavior
could still surface in some special cases that I didn't consider (not
throwing the exception scheduled by v8::ThrowException immediately, but
later on). If you happen to find such a case, please let me know!
--
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.
