jimingham wrote: I haven't looked at the code yet, but to the question of lldb input vrs. debugee input. command-line lldb already has the notion of either supporting sharing the terminal with the target or giving the target it's own IO handles (e.g. when you do `process launch --tty`.)
lldb will only push the target's IOHandler onto the stack on continue when it is explicitly sharing the terminal with the target. For instance, when you attach to a process, lldb is not sharing the terminal and the lldb command line will stay active when the target is running. Similarly with `process launch -tty` and `process launch --no-stdio`. Mixing program I/O and debugger I/O is always confusing, and we shouldn't do that except in the one case where we really can't avoid it: when running command-line lldb in a terminal where the user really wants to have the target control the terminal lldb is using while running. 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
