Good day,
I have a weird problem I can not figure out for some time now.
I’m running a Linux at home, and I’m trying to make the UE4 (built from source code) work with LLDB debugger in VS code. My problem is that when the debugger is set to LLDB the editor never shows up on the screen. I see it taking up RAM in task manager so as LLDB process, but the window never displays. On the other hand it starts just fine when the debugger is set to GDB. But its kinda slow, and I really want to try LLDB instead. The log get stuck at shader compiling, which is weird cause the shaders were already compiled previously outside of the debugging session.
Here’s my launch task:
[SPOILER] {
“name”: “TestProjectEditor (Debug)”,
“request”: “launch”,
“preLaunchTask”: “TestProjectEditor Linux Debug Build”,
“program”: “/home/username/Documents/UnrealEngine/Engine/Binaries/Linux/UE4Editor-Linux-Debug”,
“args”:
“/home/username/Documents/UnrealEngine/Games/TestProject/TestProject.uproject”
],
“cwd”: “/home/username/Documents/UnrealEngine”,
“MIMode”: “lldb”,
“type”: “cppdbg”
},
[/SPOILER]
The VS output log is provided in the attachments.
Some system info:
[SPOILER]Manjaro Linux
UE4 (4.23)
LLDB (8.0.1)
VSCode (1.36.1)
VSCode C++ extension (0.24.1)[/SPOILER]
I’d greatly appreciate if someone would even just give me a suggestion of what else I could try, because I’m out of ideas at this point.
Thanks.
Jatin-CBS
(Jatin-CBS)
November 11, 2020, 9:25am
2
opened 04:10PM - 07 Oct 18 UTC
closed 07:32AM - 05 Aug 19 UTC
confirmed
Which OS: **Linux Ubuntu 18.04.1 LTS**
Which extension version: **1.0.0**
Whic… h LLDB version: **6.0.0**
Which VSCode version: **1.27.2**
What is the problem and how did you get there:
When launching my project (Unreal Engine 4.20.3), the preLaunchTask runs (build), but then LLDB is stuck on the following steps:
```
Display settings: variable format=auto, show disassembly=auto, numeric pointer values=off, container summaries=on.
Launching /home/username/Engines/UnrealEngine/Engine/Binaries/Linux/UE4Editor-Linux-Debug /home/username/Programming/ProjectFolder/ProjectName.uproject -debug
Pooling OS allocations (pool size: 8016 MB, maximum allocations: 54195).
Using binned2.
2 locations added to breakpoint 2
2 locations added to breakpoint 2
```
**The Unreal Engine editor will launch only if I kill LLDB with VSCode Stop button (red square)**.
What did you expect to have happened instead: Unreal Engine Editor (the project to be launched) should launch through LLDB. I tried to do it manually in the Terminal and it works. So it seems to come from either VSCode or VSCode-lldb.
LLDB Output:
```
Starting new session with:
{ name: 'Launch Configuration',
request: 'launch',
preLaunchTask: 'ProjectName Linux Debug Build',
program: '/home/username/Engines/UnrealEngine/Engine/Binaries/Linux/UE4Editor-Linux-Debug',
args:
[ '/home/username/Programming/ProjectFolder/ProjectName.uproject',
'-debug' ],
cwd: '/home/username/Engines/UnrealEngine',
type: 'lldb' }
(lldb) command script import '/home/username/.vscode/extensions/vadimcn.vscode-lldb-1.0.0/adapter'
bind: Invalid command `enable-meta-key'.
(lldb) script adapter.main.run_tcp_session(0, 'e30=')
Listening on port 44991
```
My launch config:
```
{
"name": "ProjectNameEditor (Debug)",
"request": "launch",
"preLaunchTask": "ProjectNameEditor Linux Debug Build",
"program": "/home/username/Engines/UnrealEngine/Engine/Binaries/Linux/UE4Editor-Linux-Debug",
"args": [
"/home/username/Programming/ProjectFolder/ProjectName.uproject",
"-debug"
],
"cwd": "/home/username/Engines/UnrealEngine",
"type": "lldb"
}
```
Fix is to set lldb adapter type to native and for that you need to have lldb installed
sudo dnf install lldb
or if you are on ubuntu
sudo apt install lldb
Bundled unreal engine has issues with IDE’s I use system clang and system lldb always.