From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1387 invoked by alias); 17 Mar 2006 00:23:58 -0000 Received: (qmail 1379 invoked by uid 22791); 17 Mar 2006 00:23:57 -0000 X-Spam-Check-By: sourceware.org Received: from mail-out4.apple.com (HELO mail-out4.apple.com) (17.254.13.23) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 17 Mar 2006 00:23:55 +0000 Received: from relay6.apple.com (relay6.apple.com [17.128.113.36]) by mail-out4.apple.com (8.12.11/8.12.11) with ESMTP id k2H0NreS010949 for ; Thu, 16 Mar 2006 16:23:53 -0800 (PST) Received: from [17.201.22.240] (inghji.apple.com [17.201.22.240]) by relay6.apple.com (Apple SCV relay) with ESMTP id D15401A9 for ; Thu, 16 Mar 2006 16:23:53 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <20060317000417.GJ702@adacore.com> References: <17433.61359.500131.182453@kahikatea.snap.net.nz> <20060316235644.GA26469@nevyn.them.org> <20060317000417.GJ702@adacore.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <66669853-49B0-47FE-8442-573BAD63DFB0@apple.com> Content-Transfer-Encoding: 7bit From: Jim Ingham Subject: Re: MI: changing breakpoint location Date: Fri, 17 Mar 2006 03:57:00 -0000 To: GDB List 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/msg00112.txt.bz2 Just a single data point... The old NeXT gdb had a move breakpoint feature that was there because the ProjectBuilder guys had asked for it as some point in the distant past. Maybe Michael remembers about this - it was before my time. At one point we were merging from the FSF gdb and the command broke. So I went to talk to the guy who worked on the ProjectBuilder debugger at the time, and it turned out he had stopped using it a while before we broke it. IIRC, he said that since he already had code to set breakpoints with all their conditions, etc; to query out all these settings (needed for saving breakpoints between sessions) and to delete them, it was cleaner to use that code over than to have a different code path for moving breakpoints. So we dropped it, and we haven't been asked for it again. Jim On Mar 16, 2006, at 4:04 PM, Joel Brobecker wrote: >> 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