Unable to use an alternative lldb binary

[psycha0s]

OS: Windows 10
VSCode version: 1.72.2
CodeLLDB version: 1.8.1
Compiler: gcc.exe (Rev1, Built by MSYS2 project) 12.2.0
Debuggee: x86_64-w64-mingw32

When I set "lldb.library" in vscode settings to any of my lldb binaries (one from MSYS2 project, another one from WinLibs project) code-lldb just returns an error code and hangs vscode completely:

LLDB output log

Initial debug configuration: {
  name: 'debug',
  type: 'lldb',
  request: 'launch',
  program: '${workspaceFolder}/build/Debug/var_parser.exe',
  args: [],
  cwd: '${workspaceFolder}',
  __configurationTarget: 6
}
Resolved debug configuration: {
  name: 'debug',
  type: 'lldb',
  request: 'launch',
  program: '${workspaceFolder}/build/Debug/var_parser.exe',
  args: [],
  cwd: '${workspaceFolder}',
  __configurationTarget: 6,
  relativePathBase: 'd:\\workspace\\var-parser',
  _adapterSettings: {
    displayFormat: 'auto',
    showDisassembly: 'auto',
    dereferencePointers: true,
    suppressMissingSourceFiles: true,
    evaluationTimeout: 5,
    consoleMode: 'commands',
    sourceLanguages: null,
    terminalPromptClear: null,
    evaluateForHovers: true,
    commandCompletions: true,
    reproducer: false
  }
}
Error: "Could not load \"d:\\\\tools\\\\vscode\\\\data\\\\extensions\\\\vadimcn.vscode-lldb-1.8.1\\\\adapter\\\\codelldb.dll\" (err=0000007F)"
Debug adapter exit code=1 (0x1), signal=null.

[vadimcn]

Error 0x0000007E is ERROR_MOD_NOT_FOUND aka "DLL not found". Check dll dependencies of the liblldb you are loading.
Most likely you'll need to add MSys's bin directory to PATH so that loader can find them. You can do this via "lldb.adapterEnv": { "PATH": "$(env:PATH};..." } in settings.

[psycha0s]

That's strange because I have this directory in PATH, but I'll double check it tonight. Thanks for the hint.

[psycha0s]

This is indeed strange, because I've just checked and I do have all required directories in system PATH in Windows. I even set "lld.adapterEnv" like you suggested and had no luck either.

Initial debug configuration: {
  name: 'test',
  type: 'lldb',
  request: 'launch',
  program: '${command:cmake.launchTargetPath}',
  cwd: '${workspaceFolder}',
  initCommands: [ 'settings set target.x86-disassembly-flavor intel' ],
  __configurationTarget: 6
}
Resolved debug configuration: {
  name: 'test',
  type: 'lldb',
  request: 'launch',
  program: '${command:cmake.launchTargetPath}',
  cwd: '${workspaceFolder}',
  initCommands: [ 'settings set target.x86-disassembly-flavor intel' ],
  __configurationTarget: 6,
  terminal: 'external',
  relativePathBase: 'd:\\workspace\\lldb-test',
  _adapterSettings: {
    displayFormat: 'auto',
    showDisassembly: 'auto',
    dereferencePointers: true,
    suppressMissingSourceFiles: true,
    evaluationTimeout: 5,
    consoleMode: 'commands',
    sourceLanguages: null,
    terminalPromptClear: null,
    evaluateForHovers: true,
    commandCompletions: true,
    reproducer: false
  }
}
liblldb: d:\tools\msys64\ucrt64\bin\liblldb.dll
environment: { PATH: '${env:PATH};d:\\tools\\msys64\\ucrt64\\bin;' }
params: { evaluateForHovers: true, commandCompletions: true }
Error: "Could not load \"d:\\\\tools\\\\vscode\\\\data\\\\extensions\\\\vadimcn.vscode-lldb-1.8.1\\\\adapter\\\\codelldb.dll\" (err=0000007F)"
Debug adapter exit code=1 (0x1), signal=null.

$ ldd /ucrt64/bin/liblldb.dll
        ntdll.dll => /c/Windows/SYSTEM32/ntdll.dll (0x7fffdd950000)
        KERNEL32.DLL => /c/Windows/System32/KERNEL32.DLL (0x7fffdca30000)
        KERNELBASE.dll => /c/Windows/System32/KERNELBASE.dll (0x7fffdb110000)
        msvcrt.dll => /c/Windows/System32/msvcrt.dll (0x7fffdd680000)
        ucrtbase.dll => /c/Windows/System32/ucrtbase.dll (0x7fffdb580000)
        libgcc_s_seh-1.dll => /ucrt64/bin/libgcc_s_seh-1.dll (0x7fffbe650000)
        dbghelp.dll => /c/Windows/SYSTEM32/dbghelp.dll (0x7fffd96c0000)
        ole32.dll => /c/Windows/System32/ole32.dll (0x7fffdcaf0000)
        libwinpthread-1.dll => /ucrt64/bin/libwinpthread-1.dll (0x7fffad060000)
        RPCRT4.dll => /c/Windows/System32/RPCRT4.dll (0x7fffdd7e0000)
        combase.dll => /c/Windows/System32/combase.dll (0x7fffdbb20000)
        GDI32.dll => /c/Windows/System32/GDI32.dll (0x7fffdca00000)
        win32u.dll => /c/Windows/System32/win32u.dll (0x7fffdb980000)
        gdi32full.dll => /c/Windows/System32/gdi32full.dll (0x7fffdb870000)
        msvcp_win.dll => /c/Windows/System32/msvcp_win.dll (0x7fffdb4e0000)
        USER32.dll => /c/Windows/System32/USER32.dll (0x7fffdc860000)
        PSAPI.DLL => /c/Windows/System32/PSAPI.DLL (0x7fffdd720000)
        WS2_32.dll => /c/Windows/System32/WS2_32.dll (0x7fffdd100000)
        libstdc++-6.dll => /ucrt64/bin/libstdc++-6.dll (0x7fff61d60000)
        liblzma-5.dll => /ucrt64/bin/liblzma-5.dll (0x7fff60750000)
        libpython3.10.dll => /ucrt64/bin/libpython3.10.dll (0x7fff684a0000)
        libxml2-2.dll => /ucrt64/bin/libxml2-2.dll (0x7fff60780000)
        libclang-cpp.dll => /ucrt64/bin/libclang-cpp.dll (0x7fff49670000)
        zlib1.dll => /ucrt64/bin/zlib1.dll (0x7fff97b80000)
        libLLVM-15.dll => /ucrt64/bin/libLLVM-15.dll (0x7fff435a0000)
        libiconv-2.dll => /ucrt64/bin/libiconv-2.dll (0x7fff61910000)
        ADVAPI32.dll => /c/Windows/System32/ADVAPI32.dll (0x7fffdb9d0000)
        VERSION.dll => /c/Windows/SYSTEM32/VERSION.dll (0x7fffd51b0000)
        sechost.dll => /c/Windows/System32/sechost.dll (0x7fffdba80000)
        SHLWAPI.dll => /c/Windows/System32/SHLWAPI.dll (0x7fffdc800000)
        dbgcore.DLL => /c/Windows/SYSTEM32/dbgcore.DLL (0x7fffc0510000)
        SHELL32.dll => /c/Windows/System32/SHELL32.dll (0x7fffdc0b0000)
        libffi-8.dll => /ucrt64/bin/libffi-8.dll (0x7fffc15d0000)
        libzstd.dll => /ucrt64/bin/libzstd.dll (0x7fff683d0000)
        IMM32.DLL => /c/Windows/System32/IMM32.DLL (0x7fffdd730000)

[psycha0s]

I ran codelldb.exe from the command line and got this error:

As you can see my PATH has required directories but it seems like codelldb.exe looks for a specific function that is not found in my liblldb.dll.

[vadimcn]

What is the version of liblldb you are loading? CodeLLDB expects at least v10.0.

[psycha0s]

I use lldb 15.0.2 from MSYS2 project. I tried both mingw64 and ucrt64 variants.

[vadimcn]

Oh, the other reason might be that your liblldb was compiled with GNU ABI. CodeLLDB is compiled as x86_64-pc-windows-msvc, so there might be ABI differences. In which case, sorry, you won't be able to load that liblldb.

[psycha0s]

MSYS2 uses GNU ABI, so I think you're right - it must be the reason. Honestly, I'm trying to use an alternative lldb only because the bundled one doesn't stop on breakpoints. I know it's a different issue and shouldn't be discussed here, but could it be also caused by the ABI difference? I was using code-lldb before with MSYS2, but after some updates (both msys2 and code-lldb) it stopped working, so I'm trying to figure out what's wrong.

[vadimcn]

could it be also caused by the ABI difference?

Shouldn't be. Debug info parsing is independent of the internal ABI.

the bundled one doesn't stop on breakpoints.

Yeah, I've seen reports, but haven't had the time to investigate yet. TBH, wasn't entirely sure if it's a real issue or users just misconfiguring something.

after some updates (both msys2 and code-lldb) it stopped working,

You can try rolling back to older CodeLLDB to eliminate the latter. Which ABI you are building for?

[mark2185]

Where is the lldb.library part supposed to be? I'm trying to use an alternate lldb library without rebuilding vscode-lldb, but I can't seem to get it working. I tried setting a false path to see if it crashes, but no, it seems to work a-okay:

        {
            "name": "platform with custom port",
            "type": "lldb",
            "request": "attach",
            "lldb.library": "/home/mark/Downloads/gits/llvm-project/build-release/lib/liblldb.so.16git",
            "lldb.adapterEnv": {
                "ANDROID_PLATFORM_GDB_PORT": "9889",
                "ANDROID_PLATFORM_PORT": "7037",
                "ANDROID_ADB_SERVER_PORT": "5038"
            },
            "initCommands": [
                "platform select remote-android",
                "platform connect connect://localhost:6669",
            ],
            "pid": "24701"
        },

The same question goes for lldb.adapterEnv, I tried printing out os.environ within the lldb, but the keys defined in the configuration are missing.

[vadimcn]

lldb.library and lldb.adapterEnv go into workspace (or user) settings, not launch.json.

[naromero77intel]

I believe that I have a similar question... It looks like the latest CodeLLDB plug-in is using:

(base) [nromero@hds-clx-6 bin]$ ./lldb -v
lldb version 15.0.0-custom
  rust-enabled

Where can I find documentation for lldb.library and lldb.adapterEnv ? It is possible to specify the path to a different version of LLDB? Will it pick up the LLDB in $PATH?

Thanks for this wonderful plugin -- it made my life a lot easier.

[mark2185]

Where can I find documentation for lldb.library

It's just a path to the liblldb.so. You can see which one is your lldb currently using by running ldd lldb and finding liblldb in the output.

and lldb.adapterEnv ?

It's just a list of environment variables.

[naromero77intel]

Is the way to specify a different version of lldb to set lldb.library to where liblldb.so is located? So it doesn't need the location of the lldb executable?

[mark2185]

Correct.

lldb itself loads the liblldb shared library where most of the logic is implemented.