Description Marc Khouzam 2016-07-01 19:27:30 EDT

Currently, if the user types 'run' in the gdb console to restart the process, things fail in eclipse.  The main reason is that gdb is unable to restart the process because it tries to use the same TTY as for the original process, but that TTY is now closed.

There are some cleanup also needed in the handling of exited processes in eclipse to properly support this.

I was thinking of multiple approaches we can take to solve the tty issue:

1- once the process is started, immediately unset the tty in gdb.  A restart should then work.  There are two issues there though: first, there does not seem to be a way to unset the tty in GDB!  This can easily be fixed for gdb, but wouldn't help with old versions.  Second, the output will not go to an eclipse console.

2- we could extend the CDT PTY class to remain open even after the process it was associated too disappears.  We could then re-use the PTY each time the process is restarted.

3- once the process is started, immediately allocate a new PTY and set it in GDB.  That way, if the user types 'run' a new PTY would be ready.

There are surely other approaches, but I think #2 or #3 are pretty good and do-able.  I think #3 is better because we don't fiddle around with the PTY itself.