From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25296 invoked by alias); 9 Oct 2005 17:33:43 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 25285 invoked by uid 22791); 9 Oct 2005 17:33:40 -0000 Received: from eastrmmtao02.cox.net (HELO eastrmmtao02.cox.net) (68.230.240.37) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sun, 09 Oct 2005 17:33:40 +0000 Received: from white ([68.9.64.121]) by eastrmmtao02.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051009173323.SAZZ22723.eastrmmtao02.cox.net@white>; Sun, 9 Oct 2005 13:33:23 -0400 Received: from bob by white with local (Exim 3.36 #1 (Debian)) id 1EOf32-0000Fu-00; Sun, 09 Oct 2005 13:33:20 -0400 Date: Sun, 09 Oct 2005 17:33:00 -0000 From: Bob Rossi To: "jingzhao.ou" , gdb@sources.redhat.com Subject: Re: Separating "shell dir" output from GDB/MI output Message-ID: <20051009173320.GA972@white> Mail-Followup-To: "jingzhao.ou" , gdb@sources.redhat.com References: <20051009123326.GA436@white> <20051009171225.GA4295@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051009171225.GA4295@nevyn.them.org> User-Agent: Mutt/1.5.9i X-SW-Source: 2005-10/txt/msg00053.txt.bz2 > > On 10/9/05, Bob Rossi wrote: > > > I think the best idea we've had so far for solving problems like this is > > > to add an option to GDB to have it output GDB/MI data on a file > > > descriptor X. For instance, > > > gdb -i=mi -mi-out-fd=30 > > > and then when you fork/exec GDB you dup the 30 file descriptor so that > > > you can read the output. > > > > > > Eli, do you know if this approach would be portable to windows nativly? > > > I could look into implementing this feature, since it would resolve a > > > *lot* of problems regarding I/O. > > While I think this is a good idea, what other specific problems would > it solve that we haven't solved already? It solves several problems. The user no longer has to create a pty to give to GDB to separate the inferior output and the console output. (CGDB will have to anyways, since it uses the terminal). Some of the target's apparently write to STDOUT/STDERR, and that get's confused with the MI output. Also, thing's like 'shell' and potentially other case's get mixed in with the MI output. Finally, if we have several interpreters going at the same time, we could have them all output to there own descriptor. Bob Rossi