charles-zablit wrote: > No objection to the PR just curious about: > > > The post-run "target modules list" output orders the OS DLLs (ntdll, > > kernel32, ...) by load address, which differs between the in-process > > debugger and the lldb-server-on-Windows path. > > Why does that happen? I think load address means the address it's loaded at > in the inferior process so I'd have guessed it was the same either way > (ignoring any randomisation that Windows might do).
Essentially it boils down to the inprocess plugin using a `std::vector` which preserves the loading ordering and the remote plugin using a `std::map`. https://github.com/llvm/llvm-project/pull/203305 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
