From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29040 invoked by alias); 17 Jul 2006 13:49:36 -0000 Received: (qmail 29032 invoked by uid 22791); 17 Jul 2006 13:49:35 -0000 X-Spam-Check-By: sourceware.org Received: from eastrmmtao05.cox.net (HELO eastrmmtao05.cox.net) (68.230.240.34) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 17 Jul 2006 13:49:33 +0000 Received: from localhost.localdomain ([68.9.66.48]) by eastrmmtao05.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060717134931.FIUX7951.eastrmmtao05.cox.net@localhost.localdomain>; Mon, 17 Jul 2006 09:49:31 -0400 Received: from bob by localhost.localdomain with local (Exim 4.60) (envelope-from ) id 1G2TUL-0002wd-Sv; Mon, 17 Jul 2006 09:50:21 -0400 Date: Mon, 17 Jul 2006 19:28:00 -0000 From: Bob Rossi To: teawater , gdb@sourceware.org Subject: Re: How about remote MI? Message-ID: <20060717135021.GC513@brasko.net> References: <20060717005720.GA29042@nevyn.them.org> <20060717132709.GB513@brasko.net> <20060717134320.GA10281@nevyn.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060717134320.GA10281@nevyn.them.org> User-Agent: Mutt/1.5.11 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-07/txt/msg00117.txt.bz2 On Mon, Jul 17, 2006 at 09:43:20AM -0400, Daniel Jacobowitz wrote: > On Mon, Jul 17, 2006 at 09:27:10AM -0400, Bob Rossi wrote: > > There ia at least one possibility I can think of that would improve > > upon GDB/MI by having it connect back to the FE via a TCP socket. > > > > That is, it would avoid the 'tty' issue, by allowing the FE to put a > > single pty between the FE and GDB, and having all the MI protocol > > on a totally separate channel. > > I don't see any advantage over using the "set tty" command now that > we've got it... OK, the overhead of TCP would be pretty high just to solve that problem. However, there is a slight problem, and I've made it clear in past threads. That is, if a front end uses 'set tty' it doesn't know exactly which process to send signals to. Yes, this is a minor problem, and I haven't had significant issues with it yet. Bob Rossi