Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] When not to: Connect process input output to a terminal

Hi Marc,
 
Alain Magloire is the right person to comment on it, but I'll try...
This option should be removed from the launch configurations for Windows - there is no support for TTY. At least it should be unchecked. IOException is thrown and suppressed internally for every launch.
On Linux, if the input is redirected to a terminal "Restart" stops working. If you have a large executable it is much more efficient to use "Restart" instead of relaunching the entire session.
 
Cheers,
Mikhail
 

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Marc Khouzam
Sent: Friday, April 11, 2008 9:20 PM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] When not to: Connect process input output to a terminal

Hello,
the CDT launch has an option to
"Connect process input output to a terminal"
I definitely see the point of redirecting the inferior's output.  However, I am
not clear on when we would _not_ want to do that?  Is there a use case for
wanting to have the inferior's output as part of gdb's MI output?
Maybe for remote debugging?
 
I'm asking because we are thinking of making that option mandatory
for the DSF launch.
Thanks
Marc

--

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.


Back to the top