From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17798 invoked by alias); 16 Mar 2006 16:05:27 -0000 Received: (qmail 17774 invoked by uid 22791); 16 Mar 2006 16:05:27 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Thu, 16 Mar 2006 16:05:24 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FJuyX-0003cx-G1; Thu, 16 Mar 2006 11:05:21 -0500 Date: Thu, 16 Mar 2006 16:12:00 -0000 From: Daniel Jacobowitz To: Vladimir Prus Cc: gdb@sources.redhat.com Subject: Re: MI: changing breakpoint location Message-ID: <20060316160521.GA13476@nevyn.them.org> Mail-Followup-To: Vladimir Prus , gdb@sources.redhat.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-03/txt/msg00095.txt.bz2 On Thu, Mar 16, 2006 at 06:35:34PM +0300, Vladimir Prus wrote: > > Hello! > > At the moment, the MI interface does not allow one to change location of > breakpoint, say to move breakpoint from main.cpp:9 to main.cpp:11. > CLI does not support this either, but I'm interested in MI. > > Was this an explicit design decision, or it just happened this way? The use > case when it matters if when, in KDevelop, user edits the field of > breakpoint table with the location. > > Now, I have to delete the old breakpoint and create the new one, which is > workable, but not convenient. How about adding 'change breakpoint location' > functionality to MI? How much trouble is it, really, to remove and recreate the breakpoint? Presumably you know all the necessary information about the breakpoint, since you need it for the GUI. Almost all of the work of the "break" command is figuring out where the breakpoint should go. I don't see an advantage in having more commands that need to be able to work that out. -- Daniel Jacobowitz CodeSourcery