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
The VS output log is provided in the attachments.
Some system info:
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.
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:
The VS output log is provided in the attachments.
Some system info:
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.
Comment