Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VS Code debugger doesn't exit after program run #3339

Closed
SetTrend opened this issue Feb 23, 2016 · 3 comments
Closed

VS Code debugger doesn't exit after program run #3339

SetTrend opened this issue Feb 23, 2016 · 3 comments
Assignees

Comments

@SetTrend
Copy link

When debugging the following simple project (only a gulpfile.js), the debugger doesn't exit after the last line of code has been executed:

Gulp4ParallelTest.zip


{   "version": "0.2.0"
,   "configurations":
    [   {   "name": "Gulp"
        ,   "type": "node"
        ,   "request": "launch"
        ,   "program": "${workspaceRoot}/node_modules/gulp/bin/gulp.js"
        ,   "stopOnEntry": false
        ,   "args": []
        ,   "cwd": "${workspaceRoot}"
        ,   "runtimeExecutable": null
        ,   "runtimeArgs":
            [   "--nolazy"
            ]
        ,   "env":
            {   "NODE_ENV": "development"
            }
        ,   "externalConsole": false
        ,   "sourceMaps": false
        ,   "outDir": null
        }
    ]
}
@weinand
Copy link
Contributor

weinand commented Feb 23, 2016

@SetTrend the debugger only exits if node exits. Node programs have the tendency not to exit under debugging. You will find the same behaviour with node-inspector so this is not a VS Code specific problem.

@SetTrend
Copy link
Author

Thank's for enlightening me. Would you suggest this is more or less a Node bug? Then I would tend to create an issue there.

I feel it's quite confusing not to safely know whether a program has finished or not. Don't you, too?

@weinand
Copy link
Contributor

weinand commented Mar 8, 2016

@SetTrend I'm not sure whether this is a node bug. It might be difficult for the node runtime to decide whether there are any events expected and the runtime needs to continue running or not. Yes, please file an issue with node. I'm interested in their response.

@weinand weinand closed this as completed Mar 8, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants