From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1118 invoked by alias); 30 Jan 2008 06:54:45 -0000 Received: (qmail 1109 invoked by uid 22791); 30 Jan 2008 06:54:42 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 30 Jan 2008 06:54:17 +0000 Received: from kahikatea.snap.net.nz (192.31.255.123.static.snap.net.nz [123.255.31.192]) by viper.snap.net.nz (Postfix) with ESMTP id 39CD43DA3B4; Wed, 30 Jan 2008 19:54:09 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id 217178FC6D; Wed, 30 Jan 2008 19:54:05 +1300 (NZDT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18336.7948.316240.708346@kahikatea.snap.net.nz> Date: Wed, 30 Jan 2008 07:14:00 -0000 To: Vladimir Prus Cc: gdb-patches@sources.redhat.com Subject: Re: [BUG:MI] -break-list doesn't list multiple breakpoints In-Reply-To: <200801300854.28358.ghost@cs.msu.su> References: <18310.38708.144719.374963@kahikatea.snap.net.nz> <18335.55636.550226.474666@kahikatea.snap.net.nz> <20080130030614.GB13818@caradoc.them.org> <200801300854.28358.ghost@cs.msu.su> X-Mailer: VM 7.19 under Emacs 23.0.50.40 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-01/txt/msg00768.txt.bz2 > > > > > As an alternative, I guess this line alone could be removed so that > > > > > -break-insert lists the multiple breakpoint locations being set and > > > > > the adjust MI documentation to explain this. > > > > > > > > We should check what the new MI output looks like, and see if it > > > > breaks Emacs / Eclipse / Kdevelop. It might be that easy. > > > > > > It won't break Emacs becuase it doesn't use the output of -break-insert. > > > > If the new output from -break-list works OK, that is. > > It would be nice to actually *see* the examples of that new output ;-) > My theory (and why I did not implemented that for MI), is that frontends > will start showing breakpoint locations as if they were individual > breakpoint which is likely will fail. To begin with, if frontend uses integer > to represent breakpoint id, then "1.1" location id won't be representable. The manual doesn't state that the breakpoint number will be a integer. Without the file and line information, the frontend can't display breakpoint icons or display the relevant source in a window, which must be worse. -- Nick http://www.inet.net.nz/~nickrob