Debug process didn't close after finish debugging

[kiddkai]

In both io.js and node.js >= 0.12 have this issue.

OS:

osx & ubuntu 14

Reproduce steps:

• Create a file:

a.js

console.log('debug');

• run node debug a.js
• press c to continue

Then the stdout should have:

> debug
> program terminated

But currently, it only have

> debug

• When I try to press c to continue and make the process close, but it just stuck there waiting for v8 response.

It happen when I write my own debugger. It seems that the debug server should knows that the process is terminated, but it didn't.

[brendanashworth]

cross-ref: nodejs/node-v0.x-archive#25358
i'll mark as confirmed-bug because the joyent folks seem to have also

[pitosalas]

Trying it on mac, latest atom, Node 0.12.4, and it doesn't seem to work. F5 just says "finish debugging :) "

[kiddkai]

Hey @pitosalas , it seems that your configuration is not correct. Which can not find the node.js binary? Is there any error popup shows up? Anyway, please move the node-debugger conversation to https://github.com/kiddkai/atom-node-debugger.

Here is the issues for io.js.

[micene09]

Hi, i don't know how...and why...but all shortcuts are disabled.
I don't see any "Enable" checkbox in settings page, what can you do to fix it ?

OS: Windows 7 64bit

Ty

[bnoordhuis]

#2778 got reverted in 9b02442 so this issue is still relevant.

[johnelliott]

This is frustrating me too. I end up restarting my terminal (iTerm2 on this machine) to get out and start again...

[lhyhfut]

OS: OS X EI Capitian
my Node Path: "/Users/liuhongyu/.nvm/versions/node/v4.0.0/bin/node"
error: node executable could not be found

[mithung]

All shortcuts are disabled.I am using Windows 7 64 bit system.
Can someone help me out.

[jasnell]

It's possible that this was fixed recently in v5 and master. Can anyone confirm?

[jasnell]

Nope, still an issue unfortunately. /cc @thealphanerd