From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7607 invoked by alias); 7 Apr 2004 09:11:54 -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 7441 invoked from network); 7 Apr 2004 09:11:36 -0000 Received: from unknown (HELO miranda.se.axis.com) (193.13.178.2) by sources.redhat.com with SMTP; 7 Apr 2004 09:11:36 -0000 Received: from axis.com (ironmaiden.se.axis.com [10.13.8.120]) by miranda.se.axis.com (8.12.9/8.12.9/Debian-5local0.1) with ESMTP id i379AqUm000663; Wed, 7 Apr 2004 11:10:52 +0200 Message-ID: <4073C59A.7060004@axis.com> Date: Wed, 07 Apr 2004 09:11:00 -0000 From: Orjan Friberg Organization: Axis Communications User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 MIME-Version: 1.0 To: gdb-patches@sources.redhat.com CC: Daniel Jacobowitz , eliz@gnu.org Subject: Re: Display of read/access watchpoints when HAVE_NONSTEPPABLE_WATCHPOINT References: <407282F4.2080602@axis.com> <20040406142228.GA29473@nevyn.them.org> In-Reply-To: <20040406142228.GA29473@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-04/txt/msg00165.txt.bz2 Daniel Jacobowitz wrote: > > Presumably, the relevant part of the comment is the second half: "this > is for targets which cannot set read-only watchpoints". On the other > hand, it does not sound like that code will work for targets which > _can_ set read-only watchpoints. The patch was: FWIW, the other changes from Paul's patch (returning the remote stopped data address even after single-stepping past a nonsteppable watchpoint, and (perhaps more relevant for the issue at hand) freeing the value chain for the breakpoint when inserting/deleting instead of when removing it) doesn't seem to affect this behaviour. -- Orjan Friberg Axis Communications