From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1929 invoked by alias); 16 Mar 2006 15:43:28 -0000 Received: (qmail 1919 invoked by uid 22791); 16 Mar 2006 15:43:28 -0000 X-Spam-Check-By: sourceware.org Received: from eastrmmtao01.cox.net (HELO eastrmmtao01.cox.net) (68.230.240.38) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 16 Mar 2006 15:43:26 +0000 Received: from localhost.localdomain ([68.9.66.48]) by eastrmmtao01.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20060316154318.EVDC4894.eastrmmtao01.cox.net@localhost.localdomain>; Thu, 16 Mar 2006 10:43:18 -0500 Received: from bob by localhost.localdomain with local (Exim 4.52) id 1FJudp-0005C5-N5; Thu, 16 Mar 2006 10:43:57 -0500 Date: Thu, 16 Mar 2006 15:48:00 -0000 From: Bob Rossi To: Vladimir Prus Cc: gdb@sources.redhat.com Subject: Re: MI: changing breakpoint location Message-ID: <20060316154357.GC30980@brasko.net> 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.9i 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/msg00093.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? Hi Volodya, My initial opinion is that this does not make to much sense. The 2 different breakpoint really have nothing to do with each other. I would think it could be possible to add a new MI command that would allow you to arbitrarily delete, add or modify (enable/disable) as many breakpoints as you want. I think this would be a little more general purpose. Bob Rossi