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

Attaching the process gives different errors in different platforms #8315

Closed
sandy081 opened this issue Jun 28, 2016 · 1 comment
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Milestone

Comments

@sandy081
Copy link
Member

sandy081 commented Jun 28, 2016

#8196

  • VSCode Version: Insiders
  • OS Version: Windows

Steps to Reproduce:

  1. Open VSCode for a sample folder
  2. Create a new launch config to pick a node process
  3. Open VSCode for vscode-node-debug
  4. Run Server in launch config
  5. In Sample folder workspace, Run 'Attach a process'
  6. Select the node process which is from vscode-node-debug

In Windows, I get an error that
Attach to process: cannot enable debug mode for process 'id' (reason: Error: T) : Reason does not makes sense.

In Mac, I get a timeout error

May be it would be useful to provide some information or a link why this is not enabled.

@sandy081 sandy081 added the debug Debug viewlet, configurations, breakpoints, adapter issues label Jun 28, 2016
@weinand weinand added this to the June 2016 milestone Jun 29, 2016
@weinand
Copy link
Contributor

weinand commented Jun 29, 2016

@sandy081 A great find: attach to a node process didn't work on Windows at all because the electron based node doesn't have a working implementation of process._debugProcess(). This didn't show up in development because we are using a regular node there.
The fix is to run the process._debugProcess in a regular node.

@weinand weinand added the bug Issue identified by VS Code Team member as probable bug label Jun 29, 2016
@sandy081 sandy081 added the verified Verification succeeded label Jul 1, 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
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

2 participants