From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8002 invoked by alias); 12 May 2006 14:21:01 -0000 Received: (qmail 7986 invoked by uid 22791); 12 May 2006 14:21:00 -0000 X-Spam-Check-By: sourceware.org Received: from eastrmmtao02.cox.net (HELO eastrmmtao02.cox.net) (68.230.240.37) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 12 May 2006 14:20:56 +0000 Received: from localhost.localdomain ([68.9.66.48]) by eastrmmtao02.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060512142054.RRHM15470.eastrmmtao02.cox.net@localhost.localdomain>; Fri, 12 May 2006 10:20:54 -0400 Received: from bob by localhost.localdomain with local (Exim 4.52) id 1FeYWN-0005qq-Hm; Fri, 12 May 2006 10:21:35 -0400 Date: Fri, 12 May 2006 14:30:00 -0000 From: Bob Rossi To: Eli Zaretskii Cc: gdb-patches@sources.redhat.com Subject: Re: CLI and GDB/MI documentation patch Message-ID: <20060512142135.GG26655@brasko.net> Mail-Followup-To: Eli Zaretskii , gdb-patches@sources.redhat.com References: <20060512011730.GA26655@brasko.net> <20060512125433.GD26655@brasko.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i 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-05/txt/msg00246.txt.bz2 On Fri, May 12, 2006 at 04:59:46PM +0300, Eli Zaretskii wrote: > > Date: Fri, 12 May 2006 08:54:33 -0400 > > From: Bob Rossi > > Cc: gdb-patches@sources.redhat.com > > > > Old versions of mi2 will act incorrectly, where as new versions of mi2 > > will work better. > > In what release of GDB were those problems fixed? I'm not sure if it helps to think of things in terms of releases in regards to GDB/MI. Unfortunatly, many distros package a CVS release of GDB. So, any given snapshot of GDB could have this feature or not. However, with that said, Nick posted this: 2005-02-20 Andrew Cagney * mi/mi-main.c (captured_mi_execute_command): Use mi_cmd_interpreter_exec. So I believe that's the day when it started working nice. Eli, the real problem is, mi2 is the currently supported protocol, and certain versions of mi2 work and certain version don't, so I'm not sure this is a historical issue. > > Well, first off, this is incorrect: > > > > This mechanism is provided as an aid to developers of @sc{gdb/mi} > > clients and not as a reliable interface into the CLI. > > What would you suggest to say instead? In your patch, all you did > was add the word ``originally'': > > This mechanism was originally provided as an aid to developers of @sc{gdb/mi} > clients and not as a reliable interface into the CLI. The output of these > > But you never say what's its role _now_. I thought I did, but apparently I was unclear. The next 2 paragraphs were supposed to describe what it's role is now, I'm sorry to see it was written so unclear. Bob Rossi