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

Add vscode.startDebugWithoutDebugging #6425

Closed
isidorn opened this issue May 17, 2016 · 5 comments
Closed

Add vscode.startDebugWithoutDebugging #6425

isidorn opened this issue May 17, 2016 · 5 comments
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality verified Verification succeeded
Milestone

Comments

@isidorn
Copy link
Contributor

isidorn commented May 17, 2016

From #4615

Suggestions for better name are welcome

@isidorn isidorn self-assigned this May 17, 2016
@isidorn isidorn added feature-request Request for new features or functionality debug Debug viewlet, configurations, breakpoints, adapter issues labels May 17, 2016
@isidorn isidorn added this to the May 2016 milestone May 17, 2016
@isidorn
Copy link
Contributor Author

isidorn commented May 17, 2016

Ping @weinand for possible suggestions

@isidorn
Copy link
Contributor Author

isidorn commented May 17, 2016

@jcansdale now it will be possible to do the following. Notice the noDebug argument which specifies if the start debug should debug or just run

vscode.commands.executeCommand('vscode.startDebug', {
            "noDebug": true,
            "name": "Launch",
            "type": "node",
            "request": "launch",
            "program": "${workspaceRoot}/hello.js",
            "stopOnEntry": false,
            "args": [],
            "cwd": "${workspaceRoot}",
            "preLaunchTask": null,
            "runtimeExecutable": null,
            "runtimeArgs": [
                "--nolazy"
            ],
            "env": {
                "NODE_ENV": "development"
            },
            "externalConsole": false,
            "sourceMaps": false,
            "outDir": null,
            "internalConsoleOptions": "openOnFirstSessionStart"
        });

@isidorn isidorn assigned weinand and unassigned isidorn May 17, 2016
@jcansdale
Copy link

Wow, that was quick! :)

BTW, the reason I need to run without the debugger attached, is that when the debugger is attached the node.exe process never exits (VSCode remains in debug mode). Is this by design? Is there an option that would allow the process to exit when the debugger is attached?

@weinand
Copy link
Contributor

weinand commented May 17, 2016

@jcansdale the problem you are seeing is not a VS Code issue but this node bug: nodejs/node#1788
How would you use the 'run without debug' option to work around ths?

@jcansdale
Copy link

The process only fails to exit when the debugger is attached. What I'm doing doesn't always require the debugger. It is still an issue when I need the debugger.

sandy081 pushed a commit that referenced this issue May 19, 2016
@weinand weinand added the verified Verification succeeded label May 27, 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
debug Debug viewlet, configurations, breakpoints, adapter issues feature-request Request for new features or functionality verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants