sgraenitz added a comment. One issue with the `orc-lazy` JIT will be symbol renaming for lazy reexports: Upfront we only emit stubs for our function symbols and they trigger compilation of the actual code in a separate logical unit once they are called. The debug object we hand over to LLDB doesn't take that into account. (Maybe we are just inserting the wrong load address? Don't know.) Additionally, I am not sure how debug data is handled in the partitioning logic of the CompileOnDemandLayer.
If we had a `orc-greedy`mode in lli, we could easily demonstrate debugging here (for RTDyld-based platforms) and we could also port quite a number of tests to OrcV2. Might be worth thinking about, but so far we have MCJIT for that and it still works. Not sure any of this is worth noting in the docs? Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D90789/new/ https://reviews.llvm.org/D90789 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
