Quote Originally Posted by high_flyer View Post
Do you mean with the -S option?
That is the only way I could find in the docs that allows minicom to run something else.
I have no idea about how to perform it - it's just a thought. But the wrapper can always be called instead of running the final program.

Could you explain how this would work?
I don't follow, how the crashing application can spawn a new instance of it self (if this is what you mean)
Or do you mean minicom should spawn a new instance of the wrapper, but even then I don't quite follow...
The wrapper would start the target application and duplicate its stdin and stdout and create named pipes to it. Then if the app at the other end of the terminal crashed, the wrapper would keep running. Then if the app was restarted, it could start a wrapper again that would see that named pipes are already created and communicate through them. The downside is that you have two wrappers instead of one, but this could probably be worked around as well. The wrapper could even be a daemon which you would connect to from your Qt app (using the minicom) that would always be connected to the target app.

These are just thoughts - they need to be extended into a working solution, but I think the idea is reasonable - you might say that i.e. ssh servers work more or less like that, they just terminate the shell if you terminate connection.