Nerixyz wrote: > I've described a use case a couple times already. If you have a client-server > architecture, it would be really nice to be able to debug both the client and > the server in the same lldb process, because then you can add tooling on top > of lldb to do things like "step in across remote protocol dispatch". And in > client-server systems it is often the case that the client and the server run > on different OS-es. Jim
Sorry if I sounded mean before, that wasn't my intention at all. I assumed you meant just using lldb-server, but with this explanation it makes sense why you'd debug both and now I can see why you run into this. What do you think about caching at most two instances per kind (summary/snythetic/formatter) per entry? The two isn't from "client&server" but from having at most two different ones (gnu&msvc). https://github.com/llvm/llvm-project/pull/143748 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
