tfiala added a comment. The reason why it doesn't blow up in the hidden case is that liblldb.so has already internally resolved the storage, doesn't involve dynamic resolution, and has its own data location. Ditto for lldb-mi's copy. So they are separate islands.
There are two totally separate other issues here that I see, that I think are best handled by other discrete changes: 1. Fix lldb-mi to not need a separate copy of llvm. 2. Fix lldb on Linux to not require private symbols to be exposed to get access to them during debugging, when the debug info is available. Item 1 was recently introduced. Item 2 appears to be a flaw in Linux LLDB, at least in the configurations we use. I plan to tackle #2 in the near future. I seem to recall #1 happened when some refactoring was taking place that ended up requiring private details from llvm? https://reviews.llvm.org/D26093 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
