Comment #2 on issue 3289 by [email protected]: Suspended generator
activations can become invalid when debugging is enabled
http://code.google.com/p/v8/issues/detail?id=3289
Interesting, I haven't messed with relocs very much. Tentative plan, then:
1) Generator objects hold onto Code objects in addition to Function
objects.
2) Generator objects also hold onto the statement position of their
continuation. Yield expressions get allocated a statement position. If
the saved code doesn't match the code of the function at resume-time, then
resuming has to take a slow path of relocating the continuation, based on
the statement position.
This strategy seems to burn two additional words per generator object;
grumble. Yet I don't see a nice way around it. This strategy does have
the advantage of being somewhat compatible with some future crankshaft
possibility -- at least you could cope with tiering up or down while an
activation is suspended.
--
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.
