Attach to process does not list node process

[avissn]

• VSCode Version: 1.3.1
• OS Version: win 7

I have default config

{
      "name": "Attach to Process",
      "type": "node",
      "request": "attach",
      "processId": "${command.PickProcess}",
      "port": 5858,
      "sourceMaps": false,
      "outDir": null
}

When I F5 it shows "There are no entries to pick from".
I have started node in non-debug mode. It is in a VM.

[weinand]

@avissn the process picker can only list local node processes. It cannot "see" node processes running in a VM because a VM appears like a remote system.

[avissn]

I understand if I run VSC in my local system and node process in VM it wont show up but I have VSC, code and node processes all running in VM.
I added vm in my initial question just to let know if being a VM makes any difference. Ideally there should not be a difference whether I run in physical system or VM

[weinand]

@avissn can you see the "node" process in your win 7 task manager?

[avissn]

yes I can see in task manager

[avissn]

One more thing I noticed related to this issue in VSC 1.4 version. When I run node app in windows cmd it shows up list of process but doesn't show when I run node app in power shell.

[safinahmed]

I have the same issue
However if I remove this line from launch.json
"processId": "${command:PickProcess}",
The debugger is automatically attached to my process running in 5858

[weinand]

@safinahmed do you really want to attach the debugger to a node process that was not started in debug mode? If not, then please do not use the "processId" attribute.

The Attach to a process via a process ID is a special feature that should only be used if you know what you are doing. If you just want to attach the debugger to a node.js process that was started in debug mode use the "port" attribute. You don't need the "processId" attribute.