Updates:
Status: Duplicate
Mergedinto: 2838
Comment #9 on issue 2921 by [email protected]:
mjsunit/debug-step-4-in-frame is flaky and slow
http://code.google.com/p/v8/issues/detail?id=2921
This is a duplicate of issue 2838.
Short explaination: depending on whether the debugger is supposed to be
active or inactive when compiling a function, it may or may not have debug
break slots. The issue that not all parts of the debugger has the same
notion of being active.
What happens now is that under certain circumstances f gets compiled
without debug break slots, so debug breaks can only be set on ICs, so they
appear at different places.
--
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.
