Test: node2 - General bugbash

[roblourens]

• any OS @weinand
• any OS @sandy081

Effort: 3

There are a ton of little things that changed in the past month and it will be very helpful to do another general pass. Just spend a little time with it doing anything. At this point, basically anything that works in node-debug should also work in node-debug2.

From the previous testplan-item -

There are a million scenarios we need to support, so the most valuable thing you can do is grab any random Node project that you might have debugged with VS Code in the past, change "type" to "node2", and see what happens. If anything happens that isn't the same as "node", is it obvious to figure out what's wrong?

More specific things to try, don't need to do every single one:

Try some things that are checked off at microsoft/vscode-node-debug2#7
Ensure it kills the process when terminating a launch config, but not an attach
Set breakpoints before launching, and ensure they bind
In the main script, and in scripts that are loaded later
Look in the variables pane at different types and compare it to what you'd expect
Test very large arrays and other stress cases
It might get slow but it shouldn't crash
Test with and without sourcemaps
Attach config with a running process (start with --inspect=9229)

[roblourens]

@mousetraps