That's my fault. We never offered that option for DSF-GDB so when updating the Run launch for Mars,
I removed that option to have a single look-and-feel for the launch main tab. I couldn't think of a reason
you wouldn't want to connect to a terminal, and it seemed more confusing than anything to have that option.
I don't quite understand how your users trigger the hang. When exactly do they sent EOF? And how do
they do that? I tried ctrl+d from the console but nothing happened and cin>>c continued to work.
From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Corbat Thomas [thomas.corbat@xxxxxx]
Sent: September 4, 2015 11:33 AM
To: CDT General developers list. (cdt-dev@xxxxxxxxxxx)
Subject: [cdt-dev] Console Input Termination Issue
Hi
Linux and Mac users at our site have experienced issues with terminating the console input by sending EOF (ctrl + d). There used to be a workaround by unchecking the “Connect process input and output to terminal” option
in the run configuration, but this seems to be gone, or let’s say missing in the CMainTab2 (Checked in 8.8 RC2a and Master).
As an effect we have the launched executable hang while reading from console (e.g. std::cin >> c) in an unrecoverable state – no further input is sent, but the read operation does not fail either. The application has
to be terminated.
It works on Windows with ctrl+z though.
Does anybody have a clue whether there is another workaround or an option to configure this?
Kind Regards
Thomas