You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
stepping through a three lines of code crashes node 4.2.6 #4917
@bnoordhuis no, the nightly build still cannot successfully step over the second console.log. The only difference I see on OS X is that I don't get an OS alert for the crashing node application. In node 4.2.6 I got an alert.
I cannot reproduce with master, at least not with the built-in debug client (node debug 127.0.0.1:5858). The client does hang after the second step but that's #4651, an unrelated issue. The debuggee prints {} twice, as expected.
This looks like a duplicate of the hug I'm working on with util and debug
contexts. I'll add the issue number when I'm on my computer
On Jan 27, 2016 2:23 PM, "Ben Noordhuis" notifications@github.com wrote:
I cannot reproduce with master, at least not with the built-in debug
client (node debug 127.0.0.1:5858). The client does hang after the second
step but that's #4651#4651, an
unrelated issue. The debuggee prints {} twice, as expected.
—
Reply to this email directly or view it on GitHub #4917 (comment).
As a data point, when I revert commit 25776f3 (the fix from #4328), the debuggee does crash on the second step. Maybe there is more at play but for now my money is on #4328.
launch this snippet
test.js:with
node --debug-brk test.jsand attach a debugger, e.g. node-inspector or VSCode.The first step command works fine, the second step crashes node on all platforms.