[lldb-dev] lldb-server link failure with shared library configuration

[Peeter Joot via lldb-dev]

Hi Greg,

IRExecutionUnit.cpp looks like the origin of at least some of the undefined symbols:

.../llvm/include/llvm/ExecutionEngine/RTDyldMemoryManager.h:61: undefined reference to `vtable for llvm::RTDyldMemoryManager'

.../llvm/include/llvm/ExecutionEngine/JITSymbol.h:223: undefined reference to `vtable for llvm::JITSymbolResolver'

.../llvm/include/llvm/ExecutionEngine/RuntimeDyld.h:96: undefined reference to `vtable for llvm::RuntimeDyld::MemoryManager'

lib/liblldbExpression.a(IRExecutionUnit.cpp.o):(.data.rel.ro+0x90): undefined reference to `llvm::RTDyldMemoryManager::deregisterEHFrames()'

lib/liblldbExpression.a(IRExecutionUnit.cpp.o):(.data.rel.ro+0xa8): undefined reference to `llvm::RuntimeDyld::MemoryManager::anchor()'

lib/liblldbExpression.a(IRExecutionUnit.cpp.o):(.data.rel.ro+0x118): undefined reference to `llvm::JITSymbolResolver::anchor()'

lib/liblldbExpression.a(IRExecutionUnit.cpp.o):(.data.rel.ro._ZTVN4llvm18MCJITMemoryManagerE[_ZTVN4llvm18MCJITMemoryManagerE]+0x60): undefined reference to `llvm::RuntimeDyld:

:MemoryManager::anchor()'

there are a couple of undefined vtable references in headers (also above), but it's not clear to me if these also neccessarily come from IRExectionUnix.cpp.

--
Peeter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20170828/6e34bdf8/attachment-0001.html>