Breakpoints may not work if opted-in to SDK DAP experiment on Windows if drive letter casing mismatches

Describe the bug If I have code that looks like this:

void main() {
    print('print');
}

with a breakpoint set on line 2. Now if I start a debugging session. the output does show print, but the breakpoint is not hit.

To Reproduce Steps to reproduce the behavior:

1. open vscode, and ensure dart extension version 3.48 is installed.
2. Create a new file with any name and .dart at the end.
3. Type the code above with a breakpoint on the print statement.
4. Start a debugging session.
5. Notice the print statement runs but the breakpoint is not hit.

Expected behavior The breakpoint should be hit.

Screenshots

Please complete the following information:

• Operating System and version: windows 11 (up to date)
• VS Code version: 1.71.0
• Dart extension version: 3.48.1
• Dart/Flutter SDK version:2.18.0 (stable)

[DanTup]

I don’t seem to be able to repro this:

Could you confirm how you’re starting the debug session, and also capture a log:

• Run the Dart: Capture Debugging Logs command
• Run the app
• Click Cancel on the logging notification to stop logging and open the log
• Remove anything sensitive from the log
• Attach the log here (or in a gist)

Thanks!

[DanTup]

Great, thanks for confirming. I’ll re-enable the new DAPs for Windows only once #4149 is fixed (and the SDK being used contains the fix if the fix ends up being in there).