labath added a comment. In D72751#1837883 <https://reviews.llvm.org/D72751#1837883>, @aadsm wrote:
> Yeah, I'm not sure why the LoadModules function is calling > target.SetExecutableModule. It is true that the libraries-svr4 will not > include the main executable in its list. > This code was added in the context of providing qXfer:libraries support > here: https://reviews.llvm.org/D9471. I don't see any mention of including > the executable on that packet though: > https://sourceware.org/gdb/current/onlinedocs/gdb/Library-List-Format.html. > @clayborg was the main reviewer there (although this was 5 years ago or so) > and he does mention multiple times in the comments this exact issue with > calling target.SetExecutableModule. Maybe he can still remember and provide > some light here :). Thanks for digging this up, Antonio. My impression of that thread is that the author did not fully understand what Greg was asking him to do, and then that discussion got buried in other stuff. Given that qXfer is not supposed to send shared libraries, wasm is not going to be using it, and it doesn't look like this code could ever work, I'm tempted to just remove this `SetExecutable` block. :) Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D72751/new/ https://reviews.llvm.org/D72751 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
