From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9423 invoked by alias); 6 Mar 2007 19:44:43 -0000 Received: (qmail 9413 invoked by uid 22791); 6 Mar 2007 19:44:43 -0000 X-Spam-Check-By: sourceware.org Received: from mx2.palmsource.com (HELO mx2.palmsource.com) (12.7.175.14) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 06 Mar 2007 19:44:37 +0000 Received: from localhost (localhost [127.0.0.1]) by localhost.domain.tld (Postfix) with ESMTP id D7258135512; Tue, 6 Mar 2007 11:44:35 -0800 (PST) Received: from mx2.palmsource.com ([127.0.0.1]) by localhost (mx2.palmsource.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 14572-01-4; Tue, 6 Mar 2007 11:44:34 -0800 (PST) Received: from ussunex01.palmsource.com (unknown [192.168.101.9]) by mx2.palmsource.com (Postfix) with ESMTP id D901C1354EC; Tue, 6 Mar 2007 11:44:34 -0800 (PST) Received: from 192.168.92.81 ([192.168.92.81]) by ussunex01.palmsource.com ([192.168.101.9]) via Exchange Front-End Server owa.palmsource.com ([10.0.20.17]) with Microsoft Exchange Server HTTP-DAV ; Tue, 6 Mar 2007 19:44:34 +0000 Received: from svmsnyderlnx by owa.palmsource.com; 06 Mar 2007 11:44:33 -0800 Subject: Re: Disabling breakpoints does not work if rejected from remotestub From: Michael Snyder To: Sascha Cc: 'Daniel Jacobowitz' , gdb@sourceware.org In-Reply-To: <004401c75fc2$698386b0$02b2a8c0@insanenotebook> References: <000001c75a51$cc99f0c0$02b2a8c0@insanenotebook> <20070227115524.GA5164@caradoc.them.org> <001501c75a91$8843c910$02b2a8c0@insanenotebook> <1173125452.29183.17.camel@localhost.localdomain> <004401c75fc2$698386b0$02b2a8c0@insanenotebook> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 06 Mar 2007 19:44:00 -0000 Message-Id: <1173210273.29183.98.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-03/txt/msg00102.txt.bz2 On Tue, 2007-03-06 at 08:38 +0100, Sascha wrote: > Hi > > >>However, the more serious error is that at this point, the > "run" (or "step") command is aborted, returning to the gdb > prompt, but without removing the breakpoints. The error handling > code at this point ought to remove all of the breakpoints that > have been inserted. > > I guess GDB does not have to remove the breakpoints at that point - as long > as it will remember them later on. No, that's not how gdb works (unles there's a change that I don't know about). We don't leave 'em in, we always remove 'em. > You simply have to compare the "DELETE > BP1/BP2" section and the "DISABLE BP1/BP2" section in the log. > > _Deleting_ the breakpoints causes GDB to send the required "z0" (bp remove) > packets for those breakpoints which have been inserted already. > > _Disabling_ the breakpoints does nothing. No "z0" packets were send to the > stub. That's odd. Doesn't sound right. > > So I guess the fix is to make GDB send the required z0 packets for disabled > breakpoints - just like it does for deleted breakpoints. Could be.