On Tue, Jan 05, 2021 at 09:54:26AM -0500, Stefan Seefeld wrote: > > On 2021-01-05 2:39 a.m., André Hartmann wrote: > > Hi Stefan, > > > > you probably want to comment and vote on > > https://bugreports.qt.io/browse/QTCREATORBUG-19870 as ultimate solution. > > > > Until then, you can use the left part of Views > Views > Debugger Log to > > insert GDB commands. > > > > Note that you can also add gdb startup commands at Tools > Options > > > Debugger > GDB. > > How does qt-creator support applications that interact with the user via > stdin/stdout ? Does it ?
You can check "Run in terminal" in the Run Settings of the project and get a separate terminal window in that case. > My use-case is this: I'm embedding a Python interpreter into my (Qt) > application which is attached to stdin / stdout. This allows me to interact > with the application using Python commands. For automated testing I'm > providing a set of Python scripts that are fed to the program (one per > test). But the real power comes from interactive testing, which allows me to > control and introspect the application state from a Python interpreter. > > It would be very valuable to run all of this within qt-creator, so I could > follow along with the debugger. Outside qt-creator I'm already able to > start this from a gdb prompt, so I can debug this whole setup. All that's > missing is the ability to do this from within qt-creator, so > https://bugreports.qt.io/browse/QTCREATORBUG-19870 looks indeed like the > solution to this. Note that the QML console is not a "terminal" at all. No fancy control characters etc. Andre' _______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator