labath added a comment. I would implement this logic slightly differently: Have a ternary setting, let's call it `debugger.interactive`, whose values are `never, always, auto`, with `auto` (the current behavior) being the default. I think that makes it the behavior of the debugger more predictible and understandable, and it is the pattern used in other places as well (see `grep --color=WHEN`)
That said, I am slightly worried about the idea of controlling the debugger over stdio. I don't know what's your use case, but if you want to make a robust solution, I'd recommend going with scripting API. If there is something you cannot achieve using the scripting API, we'd welcome patches to add the functionality. https://reviews.llvm.org/D23290 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
