Debuger has broken

[Naresh-varma]

Describe the bug
After the latest update when I start my application in debug mode I don't see any call stack and no breakpoint is working.

To Reproduce
Steps to reproduce the behavior:

1. Go to '1.47.1' version
2. Start any application in debug mode
3. See error

Log File

VS Code Version: 1.47.1

Additional context
Add any other context about the problem here.

[Naresh-varma]

I have enabled auto-update, So it got updated to 1.47.1 and the problem has begun, earlier it was working fine.

[connor4312]

If you're using Node 8, you might be hitting microsoft/vscode#102166. Otherwise please collect a trace log using the instructions in the issue template.

[XyFreak]

This appears to be an issue when using a system installation of NodeJS 10 in combination with VS Code 1.47 (.0 or .1) (I'm running a system-install of VS Code - not sure if that matters). I've run into this issue today as well attempting to launch Electron using the MS template:

C:\Users\xxx xxx\Documents\xxxxxxxxxxx/node_modules/.bin/electron.cmd --remote-debugging-port=9223 .
internal/modules/cjs/loader.js:638
    throw err;
    ^

Error: Cannot find module '"c:/Program'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at Module._preloadModules (internal/modules/cjs/loader.js:901:12)
    at preloadModules (internal/bootstrap/node.js:601:7)
    at startup (internal/bootstrap/node.js:273:9)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
Process exited with code 1

The NodeJS version used here was v10.16.2.

After updating to the latest stable NodeJS version (v12.18.2) the issue is gone. A collegue reported that he does not have any issues using NodeJS version v12.13.1.
This propably means that for NodeJS debugging in VS Code 1.47 NodeJS 12 is required now.

A heads-up in the changelogs would've been nice ;)

[Naresh-varma]

I have been using node version 8.12.0

…

On Wed, 15 Jul, 2020, 3:21 PM XyFreak, ***@***.***> wrote: This appears to be an issue when using a system installation of NodeJS 10 in combination with VS Code 1.47 (.0 or .1) (I'm running a system-install of VS Code - not sure if that matters). I've run into this issue today as well attempting to launch Electron using the MS template: C:\Users\xxx xxx\Documents\xxxxxxxxxxx/node_modules/.bin/electron.cmd --remote-debugging-port=9223 . internal/modules/cjs/loader.js:638 throw err; ^ Error: Cannot find module '"c:/Program' at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15) at Function.Module._load (internal/modules/cjs/loader.js:562:25) at Module.require (internal/modules/cjs/loader.js:692:17) at Module._preloadModules (internal/modules/cjs/loader.js:901:12) at preloadModules (internal/bootstrap/node.js:601:7) at startup (internal/bootstrap/node.js:273:9) at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3) Process exited with code 1 The NodeJS version used here was v10.16.2. After updating to the latest stable NodeJS version (v12.18.2) the issue is gone. A collegue reported that he does not have any issues using NodeJS version v12.13.1. This propably means that for NodeJS debugging in VS Code 1.47 NodeJS 12 is *required* now. A heads-up in the changelogs would've been nice ;) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#607 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALNBH2REYSTDMZ5DRI6WLE3R3V3ZLANCNFSM4OZ3732A> .

-- Disclaimer: This message (including any attachments) is confidential and intended solely for the person or organization to whom it is addressed. It may contain privileged and confidential information. If you are not the intended recipient, you should not copy, distribute or take any action in reliance on it. If you have received this message in error, please notify us immediately by telephoning or emailing the sender. This footnote also confirms that this email message has been scanned for the presence of computer viruses.

[connor4312]

@Naresh-varma thanks for the confirmation -- see the issue I linked

@XyFreak see here microsoft/vscode#102035 (comment)

[connor4312]

A fix for this issue has now been released in VS Code 1.47.2. If you previously had to opt-out of the new debugger, you should be safe to turn it back on. Thanks again for the report!