ashgti wrote: Okay, to summarize my previous comment, I think we could address this in the following ways:
1. Listen for the broadcast class instead of a specific broadcaster. The downside here is we may see events for targets/processes we're not directly interested in. 1. In the setBreakpoint (and friends) functions, delay actually setting the breakpoint until after configuration. The downside here is the added complexity to our startup flow. 1. After `launchCommands`/`attachCommands`, check the existing breakpoints and update the state. The downside here is ensuring we've correctly checked all stateful values after the launch is complete. https://github.com/llvm/llvm-project/pull/140142 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
