From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6898 invoked by alias); 16 Feb 2005 20:03:37 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 6033 invoked from network); 16 Feb 2005 20:02:19 -0000 Received: from unknown (HELO lakermmtao12.cox.net) (68.230.240.27) by sourceware.org with SMTP; 16 Feb 2005 20:02:18 -0000 Received: from white ([68.9.64.121]) by lakermmtao12.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20050216200213.ZMPF20159.lakermmtao12.cox.net@white>; Wed, 16 Feb 2005 15:02:13 -0500 Received: from bob by white with local (Exim 3.35 #1 (Debian)) id 1D1VN7-0001in-00; Wed, 16 Feb 2005 15:02:05 -0500 Date: Thu, 17 Feb 2005 00:28:00 -0000 From: Bob Rossi To: Andrew Cagney Cc: gdb-patches@sources.redhat.com Subject: Re: MI testsuite improvements Message-ID: <20050216200205.GA6608@white> Mail-Followup-To: Andrew Cagney , gdb-patches@sources.redhat.com References: <420B8026.2060006@gnu.org> <20050210160954.GA28209@white> <420B9DEC.3060501@gnu.org> <20050210195749.GA28864@white> <420BC978.1030904@gnu.org> <20050211172931.GA30352@white> <420D08DC.3050903@gnu.org> <20050212021913.GA30900@white> <20050215041600.GA3582@white> <42135BB4.8020506@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42135BB4.8020506@gnu.org> User-Agent: Mutt/1.3.28i X-SW-Source: 2005-02/txt/msg00171.txt.bz2 On Wed, Feb 16, 2005 at 09:41:56AM -0500, Andrew Cagney wrote: > Bob Rossi wrote: > > >>Let me know what you think. If you want the dbg.log files, I can provide > >>them. > > I was kind of looking for an executive summary :-) I've attached a > trimmed diff. > > Two things: > > - it should't be using --interpreter console ... > Can you and/or: add a new -mi-tty command (+test, +doco) and use that; > invoke GDB with the --tty=... option. Your call. Either pre-approved > (but get thumbs up from Eli on the doco). > > - can the TTY output be identified in someway? > That might make debugging easier, but if it isn't possible I guess we > live with that. OK, I like this idea a lot. I'll make a new mi function that allows you to set a tty. I'll also make a new MI function that will allow you to retrieve the tty device being used, both GDB and the inferior. Finally, I think it would be helpful to have GDB actually be able to create a pty for the front end. In case you didn't know, creating a pty can be a non portable task, and GDB should be capable of doing it every where it ports to. This would help out the Front Ends a lot. What do you think? Something like -mi-tty-new -mi-tty-close? Thanks, Bob Rossi