From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29159 invoked by alias); 3 May 2004 17:49:04 -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 29152 invoked from network); 3 May 2004 17:49:03 -0000 Received: from unknown (HELO aragorn.inter.net.il) (192.114.186.23) by sources.redhat.com with SMTP; 3 May 2004 17:49:03 -0000 Received: from zaretski ([80.230.149.187]) by aragorn.inter.net.il (MOS 3.4.6-GR) with ESMTP id CUX04445; Mon, 3 May 2004 20:48:45 +0300 (IDT) Date: Mon, 03 May 2004 17:49:00 -0000 From: "Eli Zaretskii" To: Orjan Friberg Message-Id: <6654-Mon03May2004204832+0300-eliz@gnu.org> CC: kettenis@chello.nl, gdb-patches@sources.redhat.com, drow@false.org In-reply-to: <40962BF0.3030707@axis.com> (message from Orjan Friberg on Mon, 03 May 2004 13:24:32 +0200) Subject: Re: Display of read/access watchpoints when HAVE_NONSTEPPABLE_WATCHPOINT Reply-to: Eli Zaretskii 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> X-SW-Source: 2004-05/txt/msg00061.txt.bz2 > Date: Mon, 03 May 2004 13:24:32 +0200 > From: Orjan Friberg > > This for a not-yet-submitted remote target, called CRISv32. Thanks! > 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. So this target could relatively easily support an API where the target itself tells GDB which of watchpoints triggered and why, provided that we invent a way for GDB to map between its watchpoint numbers and the target-size hardware data watchpoints. Is that true? > (In addition there is also one hardware instruction breakpoint, but I > guess that doesn't matter in this context.) Used for hardware-assisted breakpoints, yes?