[C] Breakpoints not work

[Mikachu2333]

There is my settings about VSC and LLDB.
When I was about to debug a .c file, lldb just flashed and then exit automatically.
(Use UCRT runtime, GCC 11.3.0 + LLVM/Clang/LLD/LLDB 14.0.1 + MinGW-w64 10.0.0 (UCRT) - release 2 (LATEST) from https://winlibs.com/)
（I have used the -glldb arg）
vscode.zip

[Mikachu2333]

this is the frame of dir ( I've closed the workplace)

[vadimcn]

Sorry, I've no idea. Not even sure which compiler you are using there, GCC or clang. When I'm testing targets compiled with MinGW-w64 GCC, it it seems to work.
Try to see if any of these suggestions help: https:/vadimcn/vscode-lldb/wiki/Breakpoints-are-not-getting-hit

[johnmph]

Sorry I didn’t view your last replies. Yes maybe the installation provides some necessary files. Thank you and congrats to find a solution

[Mikachu2333]

I think the UCRT tool chain I downloaded from winlibs.com may lack some essential dll and affect the compilation, and then influent the dubug.

[Mikachu2333]

[Mikachu2333]

Don't forget to edit my tasks.json !
I use the arg of main.c and clang !!! (Because I'm a noob, and don't need to compile other file...🤦‍)
You should change to clang++ and please verify which file(s) you need to compile!

[Mikachu2333]

@johnmph Hi! Have you solved the problem? I have a problem super similar to yours.

Sorry, but I have to query that if you have read the solutions above carefully.

We two have give two solutions for you. #695 (comment)

Please read it carefully and ask any question if you couldn't handle it after trying. Never ask only!

If still have questions expect the above, please ask, I will always happy to resolve it as soon as possible.

[Mikachu2333]

I can't imagine that people in the world would have the same question as mine... The only difference is that I learned C but you learned Cpp...
Which complier did you use? I suspect the compiler I downloaded from winlibs.com caused the trouble.

[johnmph]

I use GCC toolchain and LLVM toolchain on Windows by using MSYS2. I forgot to say that LLDB works fine on Ubuntu by WSL2 on Windows 10.

[Mikachu2333]

Over. #695 (reply in thread)

[Selflocking]

I use MSYS2 to install clang, and had the same problem，probably because the llvm14.0.
I found two solutions, one is to install mingw-llvm 13.0 form https:/brechtsanders/winlibs_mingw/releases/tag/11.2.0-9.0.0-ucrt-r3.
the other is to install llvm14.0 from https:/llvm/llvm-project/releases/tag/llvmorg-14.0.3, it works with MSVC

[Mikachu2333]

In summary, here are two ways to solve this problem.

No.1 Use the LLVM-MinGW64 that someone have bulit, and reinstall (or build llvm project by yourself) LLVM to the folder where you realease the LLVM-MinGW64 before.

No.2 Use with MVSC toolkits (Official and no need for MinGW64).

By the way, the url you give https:/brechtsanders/winlibs_mingw/releases/tag/11.2.0-9.0.0-ucrt-r3 is really the directly url from winlibs.com I mentioned above...

[Mikachu2333]

In summary, here are two ways to solve this problem. (VSCode couldn't debug the file you want)

No.1 Use the LLVM-MinGW64 toolkit that someone has bulit before, and reinstall LLVM (or build llvm project by yourself) to the same folder where you realease the LLVM-MinGW64 before. (If confilct, cover it.)

Here is the detailed tutorial #695 (reply in thread)

If you download the archive from winlibs.com with UCRT toolkits or versions fllowing, there is no neeed to use "--target=" arg.

And https:/brechtsanders/winlibs_mingw/releases is the same as winlibs.com

If you don't need to debug and just need to compile the file, there is no need to do the things above. Just download the archive, release it to a folder and add it to Path.

No.2 Use with MVSC toolkits (Official support and no need for MinGW64, NO NEED TO TRY AGAIN AND AGAIN !!! ).

[endingly]

感觉就是这个发行版的 lldb 有问题， GDB都好好的

[Mikachu2333]

感觉就是这个发行版的 lldb 有问题， GDB都好好的

我也感觉是的……但是实在没找到别的带有gdb的发行版，自己又不会手动生成……只能这样凑合着用了

[F7kyyy]

感觉就是这个发行版的 lldb 有问题， GDB都好好的

我一直在用的是msys2安装的mingw-w64-x86_64-clang,mingw-w64-x86_64-llvm,就没办法了，需要用到msys2用到的包

[WJ430981]

i use Clang 14.0.4 x86_64-w64-windows-gnu, add these lines in settings.json, it't work!
source code in drive E:
so why the upper case E not work. and c++ debug need set the map, i mean the debuginfo packed with executable.
@vadimcn could you have a try with the msys2 compiler

    // 1. work
    // "lldb.launch.sourceMap": {
    //     ".": "e:/git/TestSpace"
    // }
    // 2. work
    "lldb.launch.sourceMap": {
        ".": "e:"
    }
    // 3. don't work
    // "lldb.launch.sourceMap": {
    //     ".": "E:"
    // }

[vadimcn]

Source path translation is internal to LLDB, I did not implement that. All sourceMap does, is initialize LLDB's target.source-map setting (with appropriate quoting and escaping). You might get better answers on LLDB forum.

In terms of things to try:

• In my experience, handling of . is unreliable. Can you adjust compilation such that an absolute path gets embedded in the binary?
• As LLDB originates from the Unix world, there might also be lingering bugs around case-insensitivity of Windows paths. Try matching filesystem casing exactly.
• Also, I'd try E:\ (with a backslash). Generally, on Windows, just E: means "the current directory, but on drive E", not sure how LLDB handles that...