New issue
Advanced search Search tips

Issue 735091 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Breakpoints are hit in the callee but not the caller.

Project Member Reported by eostroukhov@chromium.org, Jun 20 2017

Issue description

Chrome Version: 59.0.3071.104 (Official Build) (64-bit)
OS: Linux

What steps will reproduce the problem?
(1) Paste the following code as a new snippet:

function foo(v) {
  var n = 123;
  var l = "abc";
  console.log(l, n, v);
}

function bar() {
  var t = 1;
  for (var k = 0; k < 20;) {
    if (t == 300000000) {
      foo(k++);
      t = 0;
    }
    t++;
  }
  console.log("Done!", t);
}

bar();

(2) Set a breakpoint on line #2
(3) Run the snippet.
(4) Once the breakpoint is hit, set breakpoints on lines 12, 13 and 15. Clear the breakpoint on line 2.
(5) Resume the snippet execution.

What is the expected result?
Breakpoints are hit

What happens instead?
Snippet runs to the completion

 
Repro gif
out.gif
196 KB View Download
It's snippets! I'll take a look.
Not in snippet breakpoints work as expected.
I can repro the issue with the Node.
Owner: kozy@chromium.org

Comment 5 by kozy@chromium.org, Dec 13 2017

Status: Fixed (was: Assigned)
It looks fixed in latest node.js.

Sign in to add a comment