From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4302 invoked by alias); 6 Sep 2002 15:54:09 -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 4168 invoked from network); 6 Sep 2002 15:54:08 -0000 Received: from unknown (HELO valrhona.uglyboxes.com) (64.1.192.220) by sources.redhat.com with SMTP; 6 Sep 2002 15:54:08 -0000 Received: from localhost.localdomain (IDENT:gvRQr3Y9Sxjo7cK/hJ9IrbRkAnKTtsmh@localhost.localdomain [127.0.0.1]) by valrhona.uglyboxes.com (8.11.6/8.11.6) with ESMTP id g86FtdP02032; Fri, 6 Sep 2002 08:55:47 -0700 Date: Fri, 06 Sep 2002 08:54:00 -0000 From: Keith Seitz X-X-Sender: keiths@valrhona.uglyboxes.com To: Eli Zaretskii cc: gdb-patches@sources.redhat.com Subject: Re: [RFC/doc] Interpreters documentation In-Reply-To: <9003-Fri30Aug2002213054+0300-eliz@is.elta.co.il> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-09/txt/msg00088.txt.bz2 On Fri, 30 Aug 2002, Eli Zaretskii wrote: Sorry for the long delay, I misread this message... > > > Is interpreter-exec documented elsewhere in the manual (I cannot find it > > > in my sandbox, but maybe I'm not up-to-date)? If not, you should add a > > > @kindex entry here (we have a @kindex for every GDB command). > > > > interpreter-exec is a new command. It is mentioned in the gdbmi.texinfo > > file on the interpreter branch (which I have not yet submitted). > > Then please add a @pxref to the section in gdbmi.texinfo where this > command is documented in full. interpreter-exec is both an mi command and a console command. The interpreter chapter in the gdb manual (gdb.texinfo proper, that is), defines this command. I've added a @kindex for it where it is described. I can add a cross-reference to the equivalent MI command when I commit the MI changes (yes, this command is documented in gdbmi.texinfo, but only on the branch). Here's what I've done, which admittedly is the path of least resistance (aka typing ;-). Please make recommendation if you'd like to see something different. Keith [snip] + @kindex interpreter-exec + Although you may only choose a single interpreter at startup, you may execute + commands in any interpreter from the current interpreter using the appropriate + command. If you are running the console interpreter, simply use the + @code{interpreter-exec} command: [snip]