Breakpoints not resolving properly in attach configuration on Windows

[roblourens]

From @mousetraps on September 27, 2016 21:19

Testing #12600

Node v6.6.0 (32-bit), Windows

/* app.js */
var screenName = 'hello';
var sc = ""; // set breakpoint
setTimeout(function() {
    console.log('done');
    a(screenName);

    process.exit(); // set breakpoint
},1000)

function a(screenName) {
    console.log(screenName); // set breakpoint
}

From cmd line: node --inspect --debug-brk app.js, then run attach debug configuration

Copied from original issue: microsoft/vscode-node-debug2#37

[roblourens]

From @mousetraps on September 27, 2016 21:46

Diagnostic log:
vscode-node-debug2.txt

[roblourens]

Ohhh, your command prompt is using an uppercase drive letter. But if you do a launch, it launches with a lowercase drive letter.

I'm glad that I just noticed this exists - microsoft/vscode-chrome-debug-core#107 - it's the only way to fix this.

[roblourens]

Fixed

[roblourens]

Ignore...