jimingham wrote: So it seems like if we ignore module loading errors for these cases, the generic code in lldb does the right thing and produces an "as good as it can do" module entry. So why would we ever want to elide a library if the scripted side can't find a physical file for it? Whatever is producing the module after errors should always be allowed to do that, shouldn't it?
https://github.com/llvm/llvm-project/pull/127153 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
