From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9256 invoked by alias); 8 Feb 2003 15:55:12 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 9248 invoked from network); 8 Feb 2003 15:55:12 -0000 Received: from unknown (HELO mx1.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 8 Feb 2003 15:55:12 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h18FtBf10686 for ; Sat, 8 Feb 2003 10:55:11 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h18FtBa14023; Sat, 8 Feb 2003 10:55:11 -0500 Received: from [150.1.200.14] (vpn50-47.rdu.redhat.com [172.16.50.47]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h18FtAH01640; Sat, 8 Feb 2003 10:55:11 -0500 Subject: Re: GDB/MI & CLI commands From: Keith Seitz To: Bob Rossi Cc: gdb@sources.redhat.com In-Reply-To: <20030208025807.GA8872@white> References: <20030207145557.GC7980@white> <20030207151039.GD7980@white> <1044650036.1857.15.camel@lindt.uglyboxes.com> <20030208025807.GA8872@white> Content-Type: text/plain Organization: Message-Id: <1044719975.1572.9.camel@lindt.uglyboxes.com> Mime-Version: 1.0 Date: Sat, 08 Feb 2003 15:55:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2003-02/txt/msg00163.txt.bz2 On Fri, 2003-02-07 at 18:58, Bob Rossi wrote: > I would like to know if in the official release of mi ( when its basically > complete ) will accept CLI commands from the client and give back mi > responses? No: this behavior exists today ONLY because maintainers know that the MI command set is incomplete. Once the command set is considered "complete" (or 9x% complete?), I presume that this "feature" will disappear. (I say "presume" because I am not a gdb maintainer; nonetheless, I am 99% sure that it will disappear once the command set is considered [nearly?] complete.) > This is important to me since I plan on implementing a console for the > user to issue CLI commands. This is what "interpreter-exec" is for (as you suspected). > What is the difference between MI and -interpreter-exec? The MI command "-interpreter-exec" is used to execute a command in a different interpreter. This is how you would implement a console in a GUI. For example, if I have a console window somewhere, and the user enters "help", my UI code would call (eventually): -interpreter-exec console "help" And it would get back the output of the "help" command, encapsulated in MI syntax, something like: ~"List of classes of commands:\n" ~"\n" ~"aliases -- Aliases of other commands\n" [etc] The readline-like capabilities of the UI's command line are considered a UI-specific feature. For example, in Insight, we do not use readline. We emulate the most commonly used readline commands, but we do not call any readline functions at all. IMO, this is no big deal. I've never missed anything, and I've only ever gotten one patch to add "missing" features. YMMV. Hope this helps some, Keith