lldb malfunctions due to faulty python path (ModuleNotFoundError: No module named 'lldb.embedded_interpreter')
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
llvm-defaults (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
llvm-toolchain-14 (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
llvm-toolchain-15 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Starting lldb causes the following to happen:
$ lldb
Traceback (most recent call last):
File "<string>", line 1, in <module>
ModuleNotFoundE
(lldb)
This causes issues with, for instance, QtCreator, which stalls when trying to debug anything with lldb.
lldb -P gives the following path:
/usr/lib/
However, that path doesn't exist:
$ ls -l /usr/lib/
ls: cannot access '/usr/lib/
The package python3-lldb-14 provides this path, though:
/usr/lib/
Creating a symbolic link from /usr/lib/
$ ls -l /usr/lib/
lrwxrwxrwx 1 root root 45 May 10 15:23 /usr/lib/
(lldb)
Now QtCreator functions fine with lldb.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: lldb 1:14.0-55~exp2
ProcVersionSign
Uname: Linux 5.15.0-
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue May 10 15:18:41 2022
InstallationDate: Installed on 2015-02-26 (2630 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: llvm-defaults
UpgradeStatus: Upgraded to jammy on 2022-05-02 (7 days ago)
Status changed to 'Confirmed' because the bug affects multiple users.