From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5529 invoked by alias); 15 Nov 2008 22:50:18 -0000 Received: (qmail 5458 invoked by uid 22791); 15 Nov 2008 22:50:18 -0000 X-Spam-Check-By: sourceware.org Received: from smtp.nokia.com (HELO mgw-mx06.nokia.com) (192.100.122.233) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 15 Nov 2008 22:49:43 +0000 Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx06.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id mAFMnbqF018594 for ; Sun, 16 Nov 2008 00:49:38 +0200 Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 16 Nov 2008 00:49:36 +0200 Received: from bettdhcp167238.europe.nokia.com ([172.25.167.238]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Sun, 16 Nov 2008 00:49:37 +0200 From: =?iso-8859-1?q?Andr=E9_P=F6nitz?= To: gdb-patches@sourceware.org Subject: Re: [patch] MI: breakpoint "script" is a LIST Date: Sun, 16 Nov 2008 08:23:00 -0000 User-Agent: KMail/1.9.9 References: <20081113130442.GA12991@host0.dyn.jankratochvil.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811152349.27767.apoenitz@trolltech.com> X-Nokia-AV: Clean X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-11/txt/msg00401.txt.bz2 On Thursday 13 November 2008 14:12:54 Vladimir Prus wrote: > Jan Kratochvil wrote: > > > Hi, > > > > Nemiver could not parse the MI2 output. The list of commands is a `list', not > > a `tuple'. > > For how long this bug is here? Is the risk that existing frontend break higher than > inconvenience to keep the code as is? To be honest, I'd expect existing "frontend implementors" to be able to parse "MI" output that's not conforming to the specs rather well as problems like the one mentioned here are not exactly unheard of ;-} So I am personally all for rectifying the situation and produce "proper MI2 output" from now on, just for the sake of coming generations... Andre'