From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7415 invoked by alias); 3 May 2004 11:25:18 -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 7208 invoked from network); 3 May 2004 11:25:11 -0000 Received: from unknown (HELO miranda.se.axis.com) (212.209.10.220) by sources.redhat.com with SMTP; 3 May 2004 11:25:11 -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 i43BOXUm026972; Mon, 3 May 2004 13:24:33 +0200 Message-ID: <40962BF0.3030707@axis.com> Date: Mon, 03 May 2004 11:25: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: Eli Zaretskii CC: Mark Kettenis , gdb-patches@sources.redhat.com, drow@false.org Subject: Re: Display of read/access watchpoints when HAVE_NONSTEPPABLE_WATCHPOINT References: <407282F4.2080602@axis.com> <20040406142228.GA29473@nevyn.them.org> <6654-Thu15Apr2004111217+0300-eliz@gnu.org> <407E8CEF.2050007@axis.com> <407FC69A.1000701@axis.com> <1438-Sat17Apr2004112204+0300-eliz@gnu.org> <4083E930.8040005@axis.com> <4087DFB6.1030801@axis.com> <200405012117.i41LHZSR001291@elgar.kettenis.dyndns.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-05/txt/msg00058.txt.bz2 Eli Zaretskii wrote: > > I could try, but I need help: I need to know how hardware watchpoints > work on supported platforms, including remote ones. If global and > area maintainers could describe that for systems they know, I will try > to come up with a proposal. This for a not-yet-submitted remote target, called CRISv32. It has 6 hardware data watchpoints, configurable as read/write or both (i.e. access). There are no alignment or length restriction on the memory regions that are watched. When a watchpoint hits, an exception register tells which watchpoints that triggered, and whether they trigged on read or write. I have defined HAVE_NONSTEPPABLE_WATCHPOINT, to make GDB disable the watchpoint and step over it to evaluate it. (In addition there is also one hardware instruction breakpoint, but I guess that doesn't matter in this context.) -- Orjan Friberg Axis Communications