Unable to launch an executable: "/usr/bin/lldb: cannot dynamically load position-independent executable"

[twokilohertz]

Hello, recently I've been running into an issue with CodeLLDB and have been unable to use the debugger from VSCode for some reason unbeknownst to me.

When I attempt to launch the target, I'm greeted with an error: "Oops! The debug adapter has terminated abnormally."
After checking the logs, it's appears to be during the initialisation of the liblldb debug adapter, the relevant part of the log is attached below:

Launching adapter
liblldb: /usr/bin/lldb
environment: {}
settings: { evaluateForHovers: true, commandCompletions: true }
thread 'main' panicked at adapter/codelldb/bin/main.rs:57:57:
called `Result::unwrap()` on an `Err` value: "\"/usr/bin/lldb: cannot dynamically load position-independent executable\""
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Debug adapter exit code=101 (0x65), signal=null.

Which corresponds to this line in the source code. I'm using lldb version 19.1.7 on Arch Linux using Linux kernel: Linux 6.13.1-zen3-1-zen x86_64.

I am unsure if this is because of a build configuration change in either the Arch package specifically or potentially upstream. Regardless here's what file has to say:

$ file /usr/bin/lldb
/usr/bin/lldb: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 4.4.0, BuildID[sha1]=4d26439eef3ca5965f8efbe41bb5aa9d6d795231, stripped

Sure enough the binary is a position-independent executable which correlates with the error I'm getting. Unfortunately, I'm a bit stuck at this point and am not sure where to go from here.

Any help much appreciated, cheers!

[vadimcn]

lldb.library is supposed to be a path to liblldb*.so not the lldb cli binary

[twokilohertz]

Thank you very much! I must've clicked something by mistake or let another extension modify the setting without realising. Sure enough there was an errant lldb.library entry right at the bottom of my global settings.json.