sgraenitz added a comment.

That's right, but I don't see how even the static ones could be resolved. 
Wouldn't it hard-wire the objects together? In the next session we want to load 
some object files from cache while others have changed.. Maybe one day I should 
check how ccache and the likes handle it.

IIRC OSO entries in MachO files point to the object file on disk, which allows 
LLDB to load them lazily? The DWARF parsing for ELF should follow the same 
laziness: each section is only relocated once we need it. It's just not loading 
the object lazily right? However, we couldn't do that even with OSO-style 
entries, because there is no "pull mechanism" in JITLoaderGDB :) Well, for now 
it just works.

I will leave the review here for another day or so, in case there's more 
feedback.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D90769/new/

https://reviews.llvm.org/D90769

_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to