From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9844 invoked by alias); 6 Mar 2007 01:06:03 -0000 Received: (qmail 9831 invoked by uid 22791); 6 Mar 2007 01:06:02 -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 01:05:56 +0000 Received: from localhost (localhost [127.0.0.1]) by localhost.domain.tld (Postfix) with ESMTP id 49AC1130DCF; Mon, 5 Mar 2007 15:30:04 -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 05866-01-28; Mon, 5 Mar 2007 15:29:58 -0800 (PST) Received: from ussunex01.palmsource.com (unknown [192.168.101.9]) by mx2.palmsource.com (Postfix) with ESMTP id A3F351378CB; Mon, 5 Mar 2007 12:10:53 -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 ; Mon, 5 Mar 2007 20:10:53 +0000 Received: from svmsnyderlnx by owa.palmsource.com; 05 Mar 2007 12:10:52 -0800 Subject: Re: Disabling breakpoints does not work if rejected from remote stub From: Michael Snyder To: Sascha Cc: 'Daniel Jacobowitz' , gdb@sourceware.org In-Reply-To: <001501c75a91$8843c910$02b2a8c0@insanenotebook> References: <000001c75a51$cc99f0c0$02b2a8c0@insanenotebook> <20070227115524.GA5164@caradoc.them.org> <001501c75a91$8843c910$02b2a8c0@insanenotebook> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 06 Mar 2007 01:06:00 -0000 Message-Id: <1173125452.29183.17.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/msg00070.txt.bz2 On Tue, 2007-02-27 at 18:05 +0100, Sascha wrote: > Hi > > >Could you try two things for me? > > - I downloaded the latest snapshot from head (27/02) and the problem still > exists > > - I logged the MI session with debug remote set to 1 > > See attached file. Looks like several problems, really: 252^running (gdb) &"Sending packet: $Z0,200094,4#45..." Sending packet: $Z0,200094,4#45...Ack Packet received: OK &"Ack\n" &"Packet received: OK\n" &"Packet Z0 (software-breakpoint) is supported\n" &"Sending packet: $Z0,20009c,4#74..." Packet Z0 (software-breakpoint) is supported Sending packet: $Z0,20009c,4#74...Ack Packet received: OK Sending packet: $Z0,200080,4#40...Ack Packet received: E11 Warning: Cannot insert breakpoint 3. Error accessing memory address 0x200080: (undocumented errno -1). Here, gdb reports the error as "error accessing memory", which isn't really the error (a minor point, perhaps). 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. This is why the handshake state between gdb and your target is now broken. You can't insert a third breakpoint on the target, because the first two have not been removed.