From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12599 invoked by alias); 1 May 2008 18:37:22 -0000 Received: (qmail 12590 invoked by uid 22791); 1 May 2008 18:37:21 -0000 X-Spam-Check-By: sourceware.org Received: from mail.windriver.com (HELO mail.wrs.com) (147.11.1.11) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 01 May 2008 18:37:00 +0000 Received: from ALA-MAIL03.corp.ad.wrs.com (ala-mail03 [147.11.57.144]) by mail.wrs.com (8.13.6/8.13.6) with ESMTP id m41IaamN024372; Thu, 1 May 2008 11:36:38 -0700 (PDT) Received: from ala-mail06.corp.ad.wrs.com ([147.11.57.147]) by ALA-MAIL03.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 1 May 2008 11:36:20 -0700 Received: from [147.11.233.5] ([147.11.233.5]) by ala-mail06.corp.ad.wrs.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 1 May 2008 11:36:20 -0700 Message-ID: <481A0D71.8090801@windriver.com> Date: Thu, 01 May 2008 18:37:00 -0000 From: Pawel Piech User-Agent: Thunderbird 1.5.0.14ubu (X11/20080306) MIME-Version: 1.0 To: Vladimir Prus CC: gdb@sources.redhat.com Subject: Re: MI non-stop interface details References: <200804261939.37635.vladimir@codesourcery.com> <200805012059.50679.vladimir@codesourcery.com> <481A0340.7050801@windriver.com> <200805012211.51656.vladimir@codesourcery.com> In-Reply-To: <200805012211.51656.vladimir@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-05/txt/msg00015.txt.bz2 Vladimir Prus wrote: > GDB/MI is actually not a finished published protocol -- it's work in progress. > Unfortunately, frontend maintainers tended to read between the lines, and guess > the behaviour and accepted input instead of asking here. And in cases where what > they've read between the lines does not correspond to what GDB developers means, > the result is a buggy frontend :-) > > Given that MI, presently, is still not adequate for such basic tasks as > listing local variables in a function, it will change, and it might break > things, and frontend developers should provide the input to avoid surprises. > You and Marc represent Eclipse here, and Nick represent Emacs, and > I represent KDevelop, so those three are fine, but other frontend developers > should be more active here. > > Probably, I should add big warning to MI manual, saying that everything that is not > 100% clear must be asked on the list. > > - Volodya > Given how long (and for how many versions) GDB/MI has been around and how long it's been used by clients, you cannot simply make a disclaimer and change it at will without negative consequences to clients and indirectly to GDB. It's kind of like common law marriage. Common law marriage is a law in most states in the U.S. where if you live as a couple in the same house for so many years, you become legally married even if you never said the vows. :-) Cheers, Pawel