RE: [mingw gdb/mi] Separating debuggee output from MI

[Marc Khouzam <marc.khouzam@ericsson.com>]

> -----Original Message-----
> From: gdb-owner@sourceware.org 
> [mailto:gdb-owner@sourceware.org] On Behalf Of Noobody
> Sent: Tuesday, May 15, 2012 8:13 AM
> To: eran.ifrah@gmail.com
> Cc: gdb@sourceware.org
> Subject: Re: [mingw gdb/mi] Separating debuggee output from MI
> 
>  >By running this command, gdb will create a new console for 
> the debugee 
> output.
>  >i.e. all the redirected IO that you capture in your frontend will 
> always be gdb's output.
> 
> Hi,
> 
> Thanks for the tip!
> I am aware of this option, but I would prefer to be able to handle 
> input/output
> from the debugger itself. The problem is that the Windows 
> console is not
> exactly very convenient when it comes to handling standard operations 
> such as
> copying, pasting, window resizing or similar. Also, keeping 
> all the info and
> controls in one window instead of two when debugging would be 
> preferrable in my
> opinion.
> 
> As such, I've been looking for methods to get hold of the 
> debuggees output
> directly (which I probably should have mentioned in the first mail).
> 
> The method I have now seems to work fine, but I just know too 
> little of 
> gdb's
> internals to be able to tell whether this could cause problems in the 
> future.

This is a problem that Eclipse users on Windows have been facing for 
a while.  We got multiple Eclipse bug reports about it.  We usually
tell our users to use "set new-console on" as a workaroud.
Your proposed workaround is interesting but I still see it as a
workaround.  It would be great if GDB had a integrated fix for this.

Marc