Comment #1 on issue 3717 by [email protected]: Eager compilation breaks
setting break points
https://code.google.com/p/v8/issues/detail?id=3717
Here is what happens:
When we execute the script, everything gets compiled due to --nolazy.
Function g is represented by shared function info S1, which is referenced
to by the code of fun.
When we set a break point, all code, including that of fun, is thrown away
so that we can recompile with debug break slots.
When we run fun, it is compiled. Function g is again compiled, due to
--nolazy. Since the code of fun is new, g is represented by another shared
function info S2.
When we then try to find the code for g, we use
Debug::FindSharedFunctionInfoInScript and find S1. However, what we then
run the JSFunction object that points to S2.
The fix is to skip unreachable objects in
Debug::FindSharedFunctionInfoInScript.
--
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.
