From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11355 invoked by alias); 3 May 2004 15:05:20 -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 11348 invoked from network); 3 May 2004 15:05:20 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 3 May 2004 15:05:20 -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 i43F5JkI021922 for ; Mon, 3 May 2004 11:05:19 -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 i43F5Iv16134; Mon, 3 May 2004 11:05:18 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 0AA772B9D; Mon, 3 May 2004 11:05:19 -0400 (EDT) Message-ID: <40965FAE.8090009@gnu.org> Date: Mon, 03 May 2004 15:05: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: Orjan Friberg , Eli Zaretskii , Mark Kettenis Cc: 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> <40962BF0.3030707@axis.com> In-Reply-To: <40962BF0.3030707@axis.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-05/txt/msg00059.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.) Check these bug/threads threads for background info. http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=967 http://sources.redhat.com/ml/gdb-patches/2002-09/msg00739.html Andrew