Status: Accepted
Owner: [email protected]
Labels: Type-Bug Priority-Medium
New issue 2838 by [email protected]: setting break points and debugger
being active is not in sync
http://code.google.com/p/v8/issues/detail?id=2838
setting a break point calls Debug::PrepareForBreakPoint, which removes all
optimized code, but new code only gets compiled with debug information when
the debug listener is registered. So it could happen that you
1) set break point in function f
2) run function g which compiles it without break points
3) set debug listener
4) set break point in g, which doesn't trigger recompilation since we
believe g is already running debug code. The break point may end up
somewhere wrong since we don't have debug break slots in there. We only
find call ICs that are suitable breaking positions and use those.
--
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.
