jimingham wrote: Why are we sharing one SBDebugger for multiple DAP "sessions", rather than one SBDebugger per session? SBDebuggers have independent ScriptInterpreter and CommandInterpreter state, but if you present two seemingly independent debug sessions using one SBDebugger, you're going to have odd things happening like you are typing commands at one target, and the second one stops and becomes the "selected target", changing the focus of commands issued in the first interface. You can finesse this by always providing the appropriate context, but that seems fallible.
https://github.com/llvm/llvm-project/pull/237428 _______________________________________________ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
