From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12428 invoked by alias); 6 Jun 2006 01:56:21 -0000 Received: (qmail 12419 invoked by uid 22791); 6 Jun 2006 01:56:20 -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; Tue, 06 Jun 2006 01:56:18 +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 <20060606015616.XWVW26910.eastrmmtao05.cox.net@localhost.localdomain>; Mon, 5 Jun 2006 21:56:16 -0400 Received: from bob by localhost.localdomain with local (Exim 4.60) (envelope-from ) id 1FnQnt-0006uo-H2; Mon, 05 Jun 2006 21:56:21 -0400 Date: Tue, 06 Jun 2006 01:56:00 -0000 From: Bob Rossi To: Nick Roberts , gdb-patches@sources.redhat.com Subject: Re: starting gdb/mi from FE Message-ID: <20060606015621.GF10045@brasko.net> Mail-Followup-To: Nick Roberts , gdb-patches@sources.redhat.com References: <17540.53854.931145.771214@kahikatea.snap.net.nz> <20060606012001.GA7954@nevyn.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060606012001.GA7954@nevyn.them.org> User-Agent: Mutt/1.5.11 X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00055.txt.bz2 On Mon, Jun 05, 2006 at 09:20:02PM -0400, Daniel Jacobowitz wrote: > On Tue, Jun 06, 2006 at 12:54:54PM +1200, Nick Roberts wrote: > > I can't remember the previous outcome (I got lost with all the handshakes) but > > I would prefer an MI command, -mi-version say, that the FE could use. It > > could have a major and minor part: the major number to refer to the default MI > > level; and the minor to help identify small changes made within one level. Of > > course, we'd have to remember to update it, when appropriate. > > > > Pre GDB 6.5 wouldn't really work in this case either, but > > > > (gdb) > > -mi-version > > ^error,msg="Undefined MI command: mi-version" > > (gdb) > > > > wouldn't require restarting GDB, while: > > > > nickrob/21 gdb -i=mi2,mi1 myprog > > Interpreter `mi2,mi1' unrecognized > > nickrob/22 > > > > would. > > Two items. > > Nick, could you explain why the restart is a problem? The time GDB > takes to reject an interpreter doesn't seem too bad. I don't want to > optimize the wrong thing. I would prefer not to restart GDB. I'm not so sure I agree with you that the restart time is not a problem. I think it would be noticable on older machines. > Bob, since we last discussed this the interpreter commands have matured > a bit. There's even tab completion for the CLI interpreter-exec > command; try "interpreter-exec " and you'll get a list. Yes, I see that now. My patch was causing GDB to crash when doing that. I'll have to look more closely at the patch. > Would -interpreter-list and -interpreter-set do it for you? > > I thought there already was a "set interp", but it seems I was > mistaken. Well, I'm not sure. My initial guess is no. Nick, please check this part out also, especially in regards to your -mi-version command. If GDB successfully starts with a -i=miN or just using the CLI and hoping to switch to MI, then GDB is allowed to execute an arbitrary number of commands before the FE can issue even a single command. At least, in the CLI mode this is true if the user has commands in .gdbinit. I really can't afford to recieve a single MI output commadn before I determine what generated parser I am going to use. So, I'll be stuck starting GDB N times :( Bob Rossi