Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Breakpoints not resolving properly in attach configuration on Windows #37

Closed
mousetraps opened this issue Sep 27, 2016 · 4 comments
Closed
Labels

Comments

@mousetraps
Copy link

Testing microsoft/vscode#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

image

@mousetraps
Copy link
Author

mousetraps commented Sep 27, 2016

Diagnostic log:
vscode-node-debug2.txt

@roblourens
Copy link
Member

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 roblourens added the bug label Sep 27, 2016
@roblourens roblourens changed the title Breakpoints not resolving properly in attach configuration Breakpoints not resolving properly in attach configuration on Windows Sep 27, 2016
@roblourens
Copy link
Member

Fixed

@roblourens
Copy link
Member

This issue was moved to microsoft/vscode#12951

@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants