From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3156 invoked by alias); 19 Feb 2005 00:06:29 -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 3132 invoked from network); 19 Feb 2005 00:06:21 -0000 Received: from unknown (HELO lakermmtao01.cox.net) (68.230.240.38) by sourceware.org with SMTP; 19 Feb 2005 00:06:21 -0000 Received: from white ([68.9.64.121]) by lakermmtao01.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20050219000621.LZLM15939.lakermmtao01.cox.net@white>; Fri, 18 Feb 2005 19:06:21 -0500 Received: from bob by white with local (Exim 3.35 #1 (Debian)) id 1D2I8d-0002aJ-00; Fri, 18 Feb 2005 19:06:23 -0500 Date: Sat, 19 Feb 2005 23:51:00 -0000 From: Bob Rossi To: Alain Magloire Cc: Andrew Cagney , Nick Roberts , gdb-patches@sources.redhat.com Subject: Re: MI testsuite improvements Message-ID: <20050219000623.GA9877@white> Mail-Followup-To: Alain Magloire , Andrew Cagney , Nick Roberts , gdb-patches@sources.redhat.com References: <20050218180003.GA9549@white> <200502181927.OAA17870@smtp.ott.qnx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200502181927.OAA17870@smtp.ott.qnx.com> User-Agent: Mutt/1.3.28i X-SW-Source: 2005-02/txt/msg00205.txt.bz2 On Fri, Feb 18, 2005 at 02:27:24PM -0500, Alain Magloire wrote: > > > > > > Ok. Wonder if it should be ``set/show tty'', "tty ..." just a wrapper. > > > > Ok, I'm going to implement this before even thinking about anything > > else. Do you care what file the -mi-tty command's go in? or should I > > create a new file? > > > > Also, is there an easy way to use the set/show internally to GDB? This > > way, as you suggessted, there will be 3 ways to access the inferior's > > tty device name. > > > > - through the MI commands > > - through the set/show > > - and you can only set the tty through the 'tty' console command > > there is no way to get the name. This should probably be > > depricated ... > > > > Internally, they should all use the same data, so, is there an > > interface to modify the set/show value internally to GDB? > > > > Bob, > I did not see the original of your proposal, so .. > Am I correct to assume that the "show" tty will print the master side > and not the slave or vice versa ... > Meaning the frontends are interested in the other side of the pipe > not the tty given by gdb to the inferior. Hi Alain, There are 2 different ideas being suggested, - To create an mi command, that does the same thing as the console 'tty' command, and each of these internally can be wrappers around some data that can be accessed with GDB's set/show mechanism. For example, -mi-set-tty /dev/pts/1 (mi command) tty /dev/pts/1 (console command) set tty /dev/pts/1 (set command) - The second idea was to have GDB internally create a pty. That would result in a master and slave side. Neither of these are important, AFAIK, only the slavename (file name of the terminal created, ie. /dev/pts/1) is important. For example, here is what could happen 1. The user asks GDB to open a new pty and the name is given back -mi-create-pty /dev/pts/1 2. The user asks GDB to use that pty for the inferior -mi-set-tty /dev/pts/1 3. The user opens /dev/pts/1 in there own program to read the output of the inferior. 4. The user asks GDB to close the device -mi-destroy-pty /dev/pts/1 Either way, it will probably be a while before I have time to work on the second task, since I'm already swamped trying to validate the MI testsuite with a syntax checker and changing the grammar to match what GDB actually outputs. Thanks, Bob Rossi