From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17076 invoked by alias); 17 Mar 2006 00:04:29 -0000 Received: (qmail 16967 invoked by uid 22791); 17 Mar 2006 00:04:27 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 17 Mar 2006 00:04:24 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 0FEBF48CDA2; Thu, 16 Mar 2006 19:04:22 -0500 (EST) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 14888-01-10; Thu, 16 Mar 2006 19:04:21 -0500 (EST) Received: from takamaka.act-europe.fr (s142-179-108-108.bc.hsia.telus.net [142.179.108.108]) by nile.gnat.com (Postfix) with ESMTP id 1EBC848CC4C; Thu, 16 Mar 2006 19:04:21 -0500 (EST) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 2A0DD47E7F; Thu, 16 Mar 2006 16:04:17 -0800 (PST) Date: Fri, 17 Mar 2006 00:23:00 -0000 From: Joel Brobecker To: Nick Roberts , Vladimir Prus , gdb@sources.redhat.com Subject: Re: MI: changing breakpoint location Message-ID: <20060317000417.GJ702@adacore.com> References: <17433.61359.500131.182453@kahikatea.snap.net.nz> <20060316235644.GA26469@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060316235644.GA26469@nevyn.them.org> User-Agent: Mutt/1.4i 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/msg00111.txt.bz2 > BTW, this does make me think about the original request differently; it > does seem a bit awkward to have to delete and recreate breakpoints > every time the user edits a source file. Maybe it isn't. I don't > know... Just my few cents: To me, it was initially expected and normal. But then there are some issues GUIs have to be careful of, probably derived from the fact that the new breakpoint would have a different ID. They have to transfer over conditions expressions, command lists, etc. For some reason I can't put my finger on, I feel against such a feature, but then it would make things simpler for the GUI, and the user would not be confused by a different breakpoint number when the location is modified... Doesn't seem like something that would be too hard to implement either, right? Something like "move-breakpoint break-id new-location". If it added to GDB, I would make it available for CLI as well, might as well. -- Joel