Updates:
Status: Accepted
Cc: [email protected]
Labels: Type-Bug Priority-Low HW-All OS-All
Comment #2 on issue 1639 by [email protected]: Debugger breaks on
internal code when attempting to step next
http://code.google.com/p/v8/issues/detail?id=1639
Debugger does not correctly handle mutually recursive functions in the
presence of handlers. FloodHandlerWithOneShot floods the function with
handler it encounters on the stack with breakpoints and these breakpoints
trigger when we re-enter this function again.
% ./d8 --expose-debug-as debug test/mjsunit/mjsunit.js regress-1639.js
break: c(); // BREAK
break: if (f) { // NOBREAK: should not break here!
Failure (should not break on unexpected lines): expected <true> found
<false>
Approach with flooding seems incorrect because even if we restrict flooding
to the code directly inside the handler we might hit unwanted breakpoints.
Attachments:
regress-1639.js 2.7 KB
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
