lemo added a comment. > That's not changing the module list, that's changing the loaded section > information. It is the dynamic loader's job to figure out what got loaded > where, plus your stack trace show this happening after we've selected a > plugin, not in the process of negotiating for the plugin. Clearing the > section load list before setting to work seems like an appropriate thing for > a selected plugin to do.
Correct, sorry - I meant the loaded sections list. This reset is problematic for minidumps since we build the loaded sections list while loading the minidump. Is the dynamic loader relevant to loading the minidumps in any way? I'm open to any other ides on how to avoid this conflict between the minidump loading and the dynamic loader, although I'd strongly prefer to minimize the code path to the strictly minimum required. For example this dynamic loader issue is particularly unfortunate since it only happens for macOS minidumps. So one immediate consequence at least is that it complicates the test matrix (BTW, we should probably have at least one macOS & iOS minidumps for LLDB tests, what do you think?) Repository: rLLDB LLDB https://reviews.llvm.org/D51176 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
