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

Debugging Node + attach to process (PickProcess) not working (wrong debug port) #2063

Closed
jbgraug opened this issue Aug 29, 2024 · 0 comments · Fixed by #2064
Closed

Debugging Node + attach to process (PickProcess) not working (wrong debug port) #2063

jbgraug opened this issue Aug 29, 2024 · 0 comments · Fixed by #2064
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded

Comments

@jbgraug
Copy link

jbgraug commented Aug 29, 2024

Does this issue occur when all extensions are disabled?: Yes/No
Yes

  • VS Code Version: 1.92.2
  • OS Version: MacOS 14.6.1 (23G93)

Steps to Reproduce:
I'm using node v18.20.3

  1. Create an app.js file with the content setInterval(()=>{console.log('alive')}, 1000)
  2. Start 2 or more node processes with node --inspect=:9223 app.js and --inspect=:9224 app.js`, etc.
  3. Click on Run & debug and select "Attach by process ID" { "name": "Attach by Process ID", "processId": "${command:PickProcess}", "request": "attach", "skipFiles": ["<node_internals>/**"], "type": "node" },
  4. On the "PickProcess" dropdown you should see at least the 2 processes started on step 1)
  5. Pick one of them
    image
  6. Regardless the one wich is picked, the debugger won't be attached (timeout)

The default debug port 9229 seems to be used by vscode for both procesess, wich is not the specified by any of the running node processes.

@jbgraug jbgraug changed the title Debuggin Node + attach to process (PickProcess) not working (wrong debug port) Debugging Node + attach to process (PickProcess) not working (wrong debug port) Aug 29, 2024
@roblourens roblourens assigned connor4312 and unassigned roblourens Aug 29, 2024
@connor4312 connor4312 transferred this issue from microsoft/vscode Aug 30, 2024
@connor4312 connor4312 added this to the August 2024 milestone Aug 30, 2024
@connor4312 connor4312 added verified Verification succeeded bug Issue identified by VS Code Team member as probable bug and removed verified Verification succeeded labels Sep 25, 2024
@mjbvz mjbvz added the verified Verification succeeded label Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants