Comment #4 on issue 1080 by [email protected]: Breakpoint is set in wrong position
http://code.google.com/p/v8/issues/detail?id=1080
So the issue turned out to be that we still need to recompile the un-optimized code (from full-codegen) as we are not by default compiling the un-optimized code with the additional nop-instructions needed for breaking on statements which does not contain a call instruction.
Generation of this slightly more bloated code is triggered by the fact that debugging is active, so only functions compiled after debugging has started (which currently means the setting of the first break point) will support better stepping.
To fix this we either need to always include the extra information in the un-optimized code or have a way of replacing the un-optimized code.
-- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
