From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12817 invoked by alias); 5 May 2004 14:52:29 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 12807 invoked from network); 5 May 2004 14:52:28 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 5 May 2004 14:52:28 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i45EqRkI012794 for ; Wed, 5 May 2004 10:52:27 -0400 Received: from localhost.redhat.com (to-dhcp51.toronto.redhat.com [172.16.14.151]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i45EqPv15635; Wed, 5 May 2004 10:52:25 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id C7F692B9D; Wed, 5 May 2004 10:52:23 -0400 (EDT) Message-ID: <4098FFA7.90803@gnu.org> Date: Wed, 05 May 2004 14:52:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: Jim Ingham Cc: gdb-patches@sources.redhat.com Subject: Re: pending breakpoints change breakpoint number References: <6F7D1639-8F41-11D8-8CF3-000A958F4C44@apple.com> In-Reply-To: <6F7D1639-8F41-11D8-8CF3-000A958F4C44@apple.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-05/txt/msg00136.txt.bz2 > Hi, all... > > I have been looking at the pending breakpoint changes (to merge them into the Apple gdb). Overall it is nicer than the future-break version that we had, so that is great. > > However, one thing really bugs me about it. That is that it changes the breakpoint number out from under me when it manages to resolve the breakpoint. > > This is pretty annoying to a human user, since if I want to do anything to the breakpoint, I have to go find it's number again from info break. But it is very bad for a gui that is trying to run gdb from, say, the MI. The GUI has to use the breakpoint number to do things like disable the breakpoint, delete it, etc. So if the number switches out from under it, the gui can no longer operate on the breakpoint. Very bad... > > So there are two things that need to be addressed here. > > First off, if we are going to change the breakpoint number, clearly need a breakpoint_resolved event/hook/observer thingie that we can use to tell the GUI that breakpoint 2 resolved to breakpoint 5, and the GUI needs to change accordingly. This is pretty easy. If it were a gdb_event, the addition to gdb-events.sh would look like: The breakpoint number changing is a known bug in the current implementation. It was concluded that fixing it (a non-trivial task) was closely tied to fixing things like M:N breakpoints (one breakpoint with multiple locations) and hence should be made part of that task (painful but working pending breakpoints were considered better than no pending breakpoints). Seems that the N:M breakpoints have fallen by the wayside. Interested in working on that? Daniel can give you a status report of where things are at. Andrew