Windows breakpoint not working about lldb-mi HOT 4 CLOSED

At first glance escaping backslashes in the path argument of command break-insert can help

from lldb-mi.

Confirmed. I've tested the lldb-mi distributed with msys2 clang64 (mingw-w64-clang-x86_64-lldb-mi r83.2388bd7-1), and -break-insert always failed with 'not found', no matter '/' or '' used as path delimiter:
-break-insert --source "G:\test.cpp" --line 6
^error,msg="Command 'break-insert'. Breakpoint location 'G:\\test.cpp' not found"

-break-insert --source "G:/test.cpp" --line 6
^error,msg="Command 'break-insert'. Breakpoint location 'G:/test.cpp' not found"

from lldb-mi.

It seems that lldb doesn't recognize windows absolute file path starting with a drive letter and ':'

g:\>lldb test.exe
(lldb) target create "test.exe"
Current executable set to 'g:\test.exe' (x86_64).
(lldb) breakpoint set --file test.cpp --line 6
Breakpoint 1: where = test.exe`main + 38 at test.cpp:6:13, address = 0x0000000140001496
(lldb) breakpoint set --file g:\test.cpp --line 6
Breakpoint 2: no locations (pending).
WARNING:  Unable to resolve breakpoint to any actual locations.
(lldb) breakpoint set --file g:/test.cpp --line 6
Breakpoint 3: no locations (pending).
WARNING:  Unable to resolve breakpoint to any actual locations.
(lldb)

from lldb-mi.

When moving to the DAP interface instead of MI it was found that on Windows you need to compile using -gdwarf-4 instead of -ggdb.
As such I am closing this issue as I no loner need it fixed.

from lldb-mi.