From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23513 invoked by alias); 16 Mar 2006 23:12:28 -0000 Received: (qmail 23501 invoked by uid 22791); 16 Mar 2006 23:12: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 23:12:24 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FK1df-0006Zs-ES; Thu, 16 Mar 2006 18:12:15 -0500 Date: Thu, 16 Mar 2006 23:23:00 -0000 From: Daniel Jacobowitz To: Nick Roberts Cc: Vladimir Prus , gdb@sources.redhat.com Subject: Re: MI: changing breakpoint location Message-ID: <20060316231215.GA25222@nevyn.them.org> Mail-Followup-To: Nick Roberts , Vladimir Prus , gdb@sources.redhat.com References: <17433.61359.500131.182453@kahikatea.snap.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17433.61359.500131.182453@kahikatea.snap.net.nz> 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/msg00106.txt.bz2 On Fri, Mar 17, 2006 at 12:07:27PM +1300, Nick Roberts wrote: > > Now, I have to delete the old breakpoint and create the new one, which is > > workable, but not convenient. > > I don't find a problem with that, but it would be nice if when a program is > edited and recompiled that GDB could track the line number. So, for example > if the breakpoint is on line 10, say, and lines 4 and 5 are deleted, then > after recompiling and restarting, its on line 8. I think Visual Stuio has > this feature. I have no idea how easy/hard it would be to implement. Hard. RMS once asked for a simpler version of this, which is to track breakpoints by line number relative to the start of the function; but really we ought to be able to do this very well. I'm thinking something like "remember a couple lines of context, if you can find the same context, adjust the breakpoint and warn the user". But there's some risk of it landing in the wrong place; I don't know how to do it reliably but I bet a motivated developer would come up with something :-) Of course, then we'd have to let the MI interpreter know about the change too, so that the editor could refresh. I have no idea whether GUIs would want this behavior or not; wouldn't they want to track it themselves assuming you used the GUI's editor? -- Daniel Jacobowitz CodeSourcery