From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28560 invoked by alias); 17 Feb 2005 14:30:41 -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 28494 invoked from network); 17 Feb 2005 14:30:36 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 17 Feb 2005 14:30:36 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j1HEUZ2j023166 for ; Thu, 17 Feb 2005 09:30:36 -0500 Received: from localhost.redhat.com (vpn50-84.rdu.redhat.com [172.16.50.84]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j1HEUZO07430; Thu, 17 Feb 2005 09:30:35 -0500 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id C8D637D79; Thu, 17 Feb 2005 09:28:47 -0500 (EST) Message-ID: <4214AA1D.3030209@gnu.org> Date: Thu, 17 Feb 2005 16:58:00 -0000 From: Andrew Cagney User-Agent: Mozilla Thunderbird 0.8 (X11/20041020) MIME-Version: 1.0 To: Alain Magloire , Nick Roberts Cc: Bob Rossi , gdb-patches@sources.redhat.com Subject: Re: MI testsuite improvements 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> <20050216200205.GA6608@white> In-Reply-To: <20050216200205.GA6608@white> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-02/txt/msg00182.txt.bz2 Bob Rossi wrote: > 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. Ok. Wonder if it should be ``set/show tty'', "tty ..." just a wrapper. > 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? I suspect this is correct. Alain, how does the CDT currently hande the PTY problem? Would this be useful? [Nick, any thoughts] Andrew