I was struggling with this issue for over a year but found the problem in my case.

VSCode python debugger will only recognize either CRLF or LF at the end of lines but not both. The debugger will appear to skip lines (but they are still executed) when there is a mix of the two in the file. This was happening in my case because I was adding lines of code while inside a debugging session and when I saved the file with the debugger session still live the end of line characters were different than the default in the file.

To solve it I simply had to change the line feed setting on right side of the bottom blue bar in VSCode from CRLF to LF back to CRLF and save the file.

Answer from WGee on Stack Overflow
🌐
Reddit
reddit.com › r/vscode › vs code debug not stopping on breakpoints
r/vscode on Reddit: VS Code debug not stopping on breakpoints
June 10, 2023 -

I'm new to using VS Code as I¡ve always used Eclipse IDE. I'm trying to debug my java file in which I've created a breakpoint, but the debugger just runs the code as if there wasn't such breakpoint..

I've seen some other people struggle with this, so here's my launch.json:

{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Java",
            "type": "java",
            "request": "launch",
            "stopOnEntry": true,
            "jdkPath": "${env:JAVA_HOME}/bin",
            "cwd": "${fileDirname}",
            "startupClass": "${fileBasenameNoExtension}",
            "classpath": [
                ".",
                "${fileDirname}"
            ]
        },
        {
            "name": "Java Console App",
            "type": "java",
            "request": "launch",
            "stopOnEntry": true,
            "jdkPath": "${env:JAVA_HOME}/bin",
            "cwd": "${fileDirname}",
            "startupClass": "${fileBasenameNoExtension}",
            "classpath": [
                ".",
                "${fileDirname}"
            ],
            "externalConsole": true
        },
        {
            "type": "java",
            "name": "Current File",
            "request": "launch",
            "mainClass": "${file}"
        },
        {
            "type": "java",
            "name": "Numeros",
            "request": "launch",
            "mainClass": "Numeros",
            "projectName": "progra_4bad0bd0"
        }
    ]
}

Thanks in advance

🌐
GitHub
github.com › golang › vscode-go › issues › 2417
VSCode Breakpoint not hitting/stopping when run in debugger mode - Golang · Issue #2417 · golang/vscode-go
August 18, 2022 - When Start Debugging is fired, the program runs successfully. However the program doesn't stop at breakpoints. Breakpoint is enabled and placed alright.
Author   riderrocks
🌐
Reddit
reddit.com › r/rust › how to debug vscode rust debugger skipping breakpoints
r/rust on Reddit: How to debug VSCode Rust debugger skipping breakpoints
September 30, 2021 -

I use VSCode with CodeLLDB and rust-analyzer plugins as my main Rust IDE. Everything works great and I absolutely reccomend this setup.

But a few weeks ago the debbuger started missing/skipping my breakpoints. When I click "Debug" the debugger and all breakpoints change from red dots to grey empty dots. It worked again for a while few days ago for a couple of days, but doesn't work now again.

So I'm wiriting this post on Reddit because I have why this happens, and even worse, how can I find out the reason of the problem. Google search gives basically useless results. The only clue how to look for a reason is this post where the author provides a debug output, but I don't know how I can find that output.

Therefore, I would really appreciate any advice and ideas what should I check and look for to find the issue and repair it.

For anyone wondering why I didn't look for an answer earlier: I also have an access to CLion, so in those rare cases I actually need debbuger and not println! I used that. But it annoys me that I need to change IDE to debug things.

🌐
Reddit
reddit.com › r/visualstudio › my breakpoints are being skipped in my visual studio code.
r/VisualStudio on Reddit: My breakpoints are being skipped in my visual studio code.
September 7, 2025 -

I do not know if this is the right flair. I am trying to debug code, but my breakpoints are being skipped. Despite them being set to an unconditional pause with the red circle. But it just keeps going past and skipping to the end of the program. I even deleted and reseted the json file.

Find elsewhere
🌐
GitHub
github.com › microsoft › vscode-python › issues › 11716
Debugger appears to skip breakpoints with the PtvsdWheels37 experiment · Issue #235 · microsoft/debugpy
May 9, 2020 - (i.e. what is "python.jediEnabled" set to; more info How to update the language server to the latest stable version vscode-python#3977): Language Server · Value of the python.languageServer setting: "Microsoft" ... Debugger appears to skip lines (out of sync with the current state of the source file); behaves unpredictably
Author   iutlu
🌐
Developer Community
developercommunity.visualstudio.com › t › debugger-skips-without-breakpoint-and-intellisense › 1383410
Debugger skips without breakpoint, and intellisense is ...
Skip to main content · Microsoft · Visual Studio · Sign in · You need to enable JavaScript to run this app · Sorry this browser is no longer supported · Please use any other modern browser like 'Microsoft Edge'
🌐
STMicroelectronics Community
community.st.com › t5 › stm32-mcus-products › vscode-debugger-breakpoints-jump › td-p › 667461
Solved: VSCode Debugger Breakpoints jump - STMicroelectronics Community
April 27, 2024 - Object initialization silently skipped with picolibc due to missing linker symbols in STM32CubeIDE for Visual Studio Code (MCUs) 2026-03-14 · LiveWatch causes breakpoints to still be active after debugger stops in STM32CubeIDE for Visual Studio Code (MCUs) 2026-03-04 · RTOS proxy does not properly start when trying to debug with hot-attachement in STM32CubeIDE for Visual Studio Code (MCUs) 2026-03-02 · How to achieve Real-time RTOS Status Monitoring in VSCode (without manual pausing)?
🌐
Microsoft Learn
learn.microsoft.com › en-us › troubleshoot › developer › visualstudio › debuggers › troubleshooting-breakpoints
Troubleshoot breakpoints in the debugger - Visual Studio | Microsoft Learn
September 17, 2025 - If a source file has changed and the source no longer matches the code you're debugging, the debugger won't set breakpoints in the code by default. Normally, this problem happens when a source file is changed, but the source code wasn't rebuilt.
🌐
GitHub
github.com › microsoft › vscode-go › issues › 2643
Breakpoints appear to be skipped for an unknown reason. · Issue #2643 · microsoft/vscode-go
July 10, 2019 - macOS 10.14.5 vscode 1.36.1 vscode-go 0.11.4 go 1.12.7 Not sure what is causing this, but for some reason some breakpoints are being skipped. I'm assuming this may be a delve issue, but want to check here first before moving forward. I d...
Author   SteelPhase
Top answer
1 of 3
5

It looks that there is an issue in vscode (Issue opened by on github [here][1]) . But for now, the workaround is to set the protocol in the configuration (launch.json) to "inspector". With this option, the breakpoints is now reached properly.

Also, change the "--debug=5858" in the "runtimeArgs" option to "--inspect=5858"

{
  "type": "node",
  "request": "launch",
  "name": "Launch server with Nodemon",
  "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/nodemon",
  "runtimeArgs": [
    "--inspect=5858"
  ],
  "program": "${workspaceRoot}/src/server.ts",
  "restart": true,
  "port": 5858,
  "protocol": "inspector",
  "console": "integratedTerminal",
  "internalConsoleOptions": "neverOpen",
  "outFiles": ["${workspaceRoot}/build/**/*.js"],
  "sourceMaps": true
},

Also, after that, if you have a flashing message error telling you:

Cannot connect to runtime process, timeout after 10000 ms - (reason: Cannot connect to the target: connect ECONNREFUSED 127.0.0.1:5858)

It means that your program is too short and that debugger has not enough time to break on your breakpoint. To resolve that, add a second runtime argument to option "runtimeArgs": "--debug-brk" and set too "stopOnEntry" option to true

The final configuration should looks like this:

{
  "type": "node",
  "request": "launch",
  "name": "Launch server with Nodemon",
  "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/nodemon",
  "runtimeArgs": [
    "--inspect=5858",
    "--debug-brk"
  ],
  "stopOnEntry": true,
  "program": "${workspaceRoot}/src/server.ts",
  "restart": true,
  "port": 5858,
  "protocol": "inspector",
  "console": "integratedTerminal",
  "internalConsoleOptions": "neverOpen",
  "outFiles": ["${workspaceRoot}/build/**/*.js"],
  "sourceMaps": true
}

It should break on the first line of your entry javascript file. Then you can press F5 and it will reach your own breakpoint.

If you don't want to press F5 each time you run your program, you can instead embed your main entry code inside a setTimeOut function with at least 1000 ms of timeout.

All these options will give enough of time to vscode to break on your breakpoints.

://github.com/Microsoft/vscode/issues/23900 "GitHub Issue"

2 of 3
2

@ManfredSteiner

I had this issue recently too. I guess you've tried to break just in the beginning of your entry file (main.ts). I've heard that we have this error message because the program is too short and terminates before the debugger can attach successfully. You have 2 solutions:

  • First, put your entry code inside a setTimeOut function with at least 1000 ms. It should give enough of time to debugger to attach to your program.

  • The second solution is to set to your launch.json the options: "stopOnEntry" to "true" and set the runtimeArgs option to ["--inspect=5858", "--debug-brk"].

Like this: "configurations": [ { "type": "node", "request": "launch", "name": "nodemon", "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/nodemon", "runtimeArgs": [ "--inspect=5858", "--debug-brk" ], "stopOnEntry": true, "program": "${workspaceRoot}/src/server/main.ts", "restart": true, "port": 5858, "protocol": "inspector", "console": "integratedTerminal", "internalConsoleOptions": "neverOpen", "outFiles": ["${workspaceRoot}/dist/**/*.js"], "sourceMaps": true } ]

It will break at the first line of your main.js and then, by pressing F5, you will be able to break on your own breakpoint in main.ts. If you don't want, each time you run your program, to press F5 until it reaches your breakpoint, I suggest you to use the first solution (Embed your main.ts entry code inside a setTimeOut function with a least 1000 ms). I hope it will help you

🌐
Visual Studio Code
code.visualstudio.com › docs › nodejs › nodejs-debugging
Node.js debugging in VS Code
November 3, 2021 - If you set a breakpoint in a skipped file, you will stop at that breakpoint, and you will be able to step through it until you step out of it, at which point normal skipping behavior will resume.
🌐
GitHub
github.com › golang › vscode-go › issues › 3743
Breakpoints are ignored during debugging, and VS code jumps to proc.go · Issue #3743 · golang/vscode-go
April 2, 2025 - When debugging a test, VS Code does not pause execution at the breakpoints that I've set in my code. Instead, it pauses at line 425 in the file proc.go.
Author   Lunkers