JDevlieghere wrote: > I think this makes sense if you plan on having the script interpreter plugins > load ASAP (meaning the shared lib is loaded during or just after > initialization). If we ever want them to be lazy, there's a real chance > somebody could query the helper before it's set and then load python later > on. (Thinking about the lldb driver scenario, not importing from python)
Yes, that's right. I don't know if you reviewed this before or after I reworked this PR. I didn't realize that the Python script interpreter plugin was calling `GetShlibDir` during its initialization, hitting this exact scenario. Anyway, the updated patch has an assert that should capture this mistake, though it still only gets diagnosed at runtime. https://github.com/llvm/llvm-project/pull/183637 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
