[Help Wanted] Unable to Get Correct Source File Path

[Alecton4]

Environment:

• Win10
• MSYS2 UCRT clang: 14.0.3
• vscode-lldb: v1.7.0

Symptom:
Seems lldb is not correctly configured (see the 5th line of the output info of debug console below), but I have no idea what to do next :(

Console is in 'commands' mode, prefix expressions with '?'.
Executing script: preRunCommands
Module D:\workspace\_Cpp\book_ProgrammingPrinciplesAndPracticeUsingCpp\ch04/e10.exe
    None
    /workspace/_Cpp/book_ProgrammingPrinciplesAndPracticeUsingCpp/d:\workspace\_Cpp\book_ProgrammingPrinciplesAndPracticeUsingCpp\ch04/e10.cpp
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
Current breakpoints:
1: file = 'd:\workspace\_Cpp\book_ProgrammingPrinciplesAndPracticeUsingCpp\ch04\e10.cpp', line = 39, exact_match = 0


2: file = 'd:\workspace\_Cpp\book_ProgrammingPrinciplesAndPracticeUsingCpp\ch04\e10.cpp', line = 53, exact_match = 0


3: file = 'd:\workspace\_Cpp\book_ProgrammingPrinciplesAndPracticeUsingCpp\ch04\e10.cpp', line = 66, exact_match = 0


4: file = 'd:\workspace\_Cpp\book_ProgrammingPrinciplesAndPracticeUsingCpp\ch04\e10.cpp', line = 84, exact_match = 0


5: Exception breakpoint (catch: off throw: on) the correct runtime exception handler will be determined when you run
Launching: D:\workspace\_Cpp\book_ProgrammingPrinciplesAndPracticeUsingCpp\ch04\e10.exe
Launched process 47304
Stop reason: Exception 0x80000003 encountered at address 0x7ffeb3cc06b0
Stop reason: Exception 0x80000003 encountered at address 0x7ffeb3cc06b0
Process exited with code 0.

Tried:
I modified my launch.json according to our Q&A. But it's still not working:

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "LLDB(Clang++)",
            "type": "lldb",
            "request": "launch",
            "program": "${workspaceFolder}/${relativeFileDirname}/${fileBasenameNoExtension}.exe",
            "args": [],
            "stopOnEntry": true,
            "cwd": "${fileDirname}",
            "sourceMap": {
                "${fileDirname}": "${relativeFileDirname}"
            },
            "preRunCommands": [
                "debug_info",
                "breakpoint list --verbose",
            ],
            "preLaunchTask": "ClangCompile",
        }
    ]
}

my ClangCompile Task is:

{
    "label": "ClangCompile",
    "command": "clang++.exe",
    "args": [
        "${file}",
        "-o",
        "${fileDirname}/${fileBasenameNoExtension}.exe",
        "-g",
        "-Wall",
        "-Wextra",
        "-static-libgcc",
        "-xc++",
        "-std=c++14",
        "-fcolor-diagnostics",
        "-v"
    ],
    "type": "process",
    "group": {
        "kind": "build",
        "isDefault": true
    },
    "presentation": {
        "echo": true,
        "reveal": "always",
        "focus": false,
        "panel": "shared"
    }
},

[vadimcn]

Your debug info says that your source file is at /workspace/_Cpp/book_ProgrammingPrinciplesAndPracticeUsingCpp/d:\workspace\_Cpp\book_ProgrammingPrinciplesAndPracticeUsingCpp\ch04/e10.cpp whereas VSCode believes it's at d:\workspace\_Cpp\book_ProgrammingPrinciplesAndPracticeUsingCpp\ch04\e10.cpp. Not sure what's going on exactly... Maybe you are building your binary with your current directory being is in the WSL file system?

[Alecton4]

/workspace/_Cpp/book_ProgrammingPrinciplesAndPracticeUsingCpp should be the workspace path (${workspaceFolder}) in unix style. Because my current workspace is d:\workspace\_Cpp\book_ProgrammingPrinciplesAndPracticeUsingCpp\. But I don't know how lldb get this path...

Adding "options": {"cwd": "${workspaceFolder}"} to compilation task doesn't work.

I also tried to change all my configs to avoid any appearance of ${workspaceFolder}, but that prefix still exists...

[Alecton4]

By the way, I'm currently using a multi-root workspace in VSCode. But I changed to a single-root workspace just now and the problem still exists.

[vadimcn]

But I don't know how lldb get this path...

From the debug info. A better question is "Where clang gets it?"

[Alecton4]

Could you tell me what this debug info indicates? I don't know whether this debug info is generated by lldb or clang. If there is any documentation on this debug info, could you please send me the link? Thanks!

[vadimcn]

Could you tell me what this debug info indicates?

You may want to read this: https://eli.thegreenplace.net/2011/02/07/how-debuggers-work-part-3-debugging-information
Also this: https://github.com/vadimcn/vscode-lldb/wiki/Windows

The path with prefix was written into debugging information section by the compiler.

[Alecton4]

@vadimcn funny observation:

When I change my compilation task to using g++, the /workspace/_Cpp/book_ProgrammingPrinciplesAndPracticeUsingCpp prefix is gone (but still cannot debug):

Console is in 'commands' mode, prefix expressions with '?'.
Executing script: preRunCommands
Module d:\workspace\_Cpp\book_ProgrammingPrinciplesAndPracticeUsingCpp\ch04/e10.exe
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
    None
Current breakpoints:
1: file = 'd:\workspace\_Cpp\book_ProgrammingPrinciplesAndPracticeUsingCpp\ch04\e10.cpp', line = 39, exact_match = 0


2: file = 'd:\workspace\_Cpp\book_ProgrammingPrinciplesAndPracticeUsingCpp\ch04\e10.cpp', line = 53, exact_match = 0


3: file = 'd:\workspace\_Cpp\book_ProgrammingPrinciplesAndPracticeUsingCpp\ch04\e10.cpp', line = 66, exact_match = 0


4: file = 'd:\workspace\_Cpp\book_ProgrammingPrinciplesAndPracticeUsingCpp\ch04\e10.cpp', line = 84, exact_match = 0


5: Exception breakpoint (catch: off throw: on) the correct runtime exception handler will be determined when you run
Launching: d:\workspace\_Cpp\book_ProgrammingPrinciplesAndPracticeUsingCpp\ch04\e10.exe
Launched process 29596
Stop reason: Exception 0x80000003 encountered at address 0x7ff8273a06b0
Stop reason: Exception 0x80000003 encountered at address 0x7ff8273a06b0
Process exited with code 0.

The compile task:

{
    "label": "G++Compile",
    "command": "g++.exe", 
    "args": [
        "${file}", 
        "-o",
        "${fileDirname}/${fileBasenameNoExtension}.exe", 
        "-g", 
        "-m64", 
        "-Wall", 
        "-Wextra",
        "-static-libgcc", 
        "-xc++",
        "-std=c++14", 
    ],
    "type": "process",
    "group": {
        "kind": "build",
        "isDefault": true 
    },
    "presentation": {
        "echo": true,
        "reveal": "always", 
        "focus": false, 
        "panel": "shared" 
    },
},

[vadimcn]

but still cannot debug

The output of debug_info command indicates that there is no debugging information for your binary. Which is strange, since you are clearly compiling with -g flag... See this: https://github.com/vadimcn/vscode-lldb/wiki/How-can-I-tell-if-a-binary-was-compiled-with-debug-symbols%3F