So, from the error message it looks like lldb is getting confused by
the debug information inside the executable. I don't have any special
hints for debugging that, I think the usual process of attaching the
debugger, examining the backtrace, and seeing what data is triggering
the assert would work
Well, after I've added .gnu_debuglink section to stripped libUE4.so LLDB
managed to resolve the symbols.
But sometimes it asserts with the following message:
---
Microsoft Visual C++ Runtime Library
---
Assertion failed!
Program: ...ORPORATION\NSIGHT
Hi Mikhail,
Modifying the build tool to include the build ID would probably be the
easiest solution to your problem. Please not that both the stripped
AND unstripped versions of the module need to have the (same)
.note.gnu.build-id section. I am not familiar with the build tool, but
"fixing" this
Hello, fellow developers!
I’m trying to debug Unreal Engine 4 sample on Android with LLDB 3.8 build from
source - Win32 x86 liblldb.dll and Android ARM lldb-server : it can’t match the
stripped module libUE4.so running on the device with a full version which is
available on a host.
Unreal Buil
