From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6671 invoked by alias); 17 May 2012 14:42:32 -0000 Received: (qmail 6660 invoked by uid 22791); 17 May 2012 14:42:31 -0000 X-SWARE-Spam-Status: No, hits=-4.0 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL X-Spam-Check-By: sourceware.org Received: from imr4.ericy.com (HELO imr4.ericy.com) (198.24.6.9) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 17 May 2012 14:42:19 +0000 Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q4HEgDOt008359; Thu, 17 May 2012 09:42:15 -0500 Received: from EUSAACMS0703.eamcs.ericsson.se ([169.254.1.69]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Thu, 17 May 2012 10:42:10 -0400 From: Marc Khouzam To: "'Noobody'" , "'eran.ifrah@gmail.com'" CC: "'gdb@sourceware.org'" Date: Thu, 17 May 2012 14:42:00 -0000 Subject: RE: [mingw gdb/mi] Separating debuggee output from MI Message-ID: References: <4FB1F5B5.6090701@noobody.org> <4FB24851.3070105@noobody.org> In-Reply-To: <4FB24851.3070105@noobody.org> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-05/txt/msg00077.txt.bz2 > -----Original Message----- > From: gdb-owner@sourceware.org=20 > [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 >=20 > >By running this command, gdb will create a new console for=20 > the debugee=20 > output. > >i.e. all the redirected IO that you capture in your frontend will=20 > always be gdb's output. >=20 > Hi, >=20 > Thanks for the tip! > I am aware of this option, but I would prefer to be able to handle=20 > input/output > from the debugger itself. The problem is that the Windows=20 > console is not > exactly very convenient when it comes to handling standard operations=20 > such as > copying, pasting, window resizing or similar. Also, keeping=20 > all the info and > controls in one window instead of two when debugging would be=20 > preferrable in my > opinion. >=20 > As such, I've been looking for methods to get hold of the=20 > debuggees output > directly (which I probably should have mentioned in the first mail). >=20 > The method I have now seems to work fine, but I just know too=20 > little of=20 > gdb's > internals to be able to tell whether this could cause problems in the=20 > future. This is a problem that Eclipse users on Windows have been facing for=20 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