jasonmolenda wrote: > What's the exact situation that triggered these extra packets. Could it be > simulated from a gdb-remote client test (i.e., by mocking server responses)?
We've always done it when we step over our dynamic loader notification breakpoint (when new solibs are loaded and lldb is informed), I think it depends on the ordering that we invoke these methods in ProcessGDBRemote, I didn't try to debug what shifted in our call ordering to make this become a hotter problem recently. (that's why my test case dlopen's a solib, because that was a specific issue) https://github.com/llvm/llvm-project/pull/109499 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
