I haven’t exposed any way to introspect JITDylib contents yet (except for the debug logging call that you found). All that you can do is issue a lookup for a symbol name and either get a result, or an error saying that no such symbol is present.
This is primarily because JITDylibs are open to mutation from multiple threads: Any snapshot that you take of a JITDylib risks being outdated a moment later. We could add an atomic “whileLockedDo(Action)’ style API, but so far it has not been necessary.
What is your use case?
— Lang.
Sent from my iPad
> On Dec 4, 2019, at 5:52 AM, che pal via llvm-dev <llvm...@lists.llvm.org> wrote:
>
> Greetings.