From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-41954-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 10660 invoked by alias); 13 Dec 2005 20:20:03 -0000
Received: (qmail 10641 invoked by uid 22791); 13 Dec 2005 20:20:02 -0000
X-Spam-Check-By: sourceware.org
Received: from romy.inter.net.il (HELO romy.inter.net.il) (192.114.186.66)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 13 Dec 2005 20:20:01 +0000
Received: from HOME-C4E4A596F7 (IGLD-84-228-161-234.inter.net.il [84.228.161.234]) 	by romy.inter.net.il (MOS 3.7.2-GA) 	with ESMTP id DEE39833 (AUTH halo1); 	Tue, 13 Dec 2005 22:19:45 +0200 (IST)
Date: Wed, 14 Dec 2005 18:12:00 -0000
Message-Id: <uu0dcrbpz.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Wu Zhou <woodzltc@cn.ibm.com>
CC: drow@false.org, gdb-patches@sources.redhat.com, mark.kettenis@xs4all.nl,         bje@au1.ibm.com, anton@au1.ibm.com
In-reply-to: <Pine.LNX.4.63.0512131318090.30718@linux.site> (message from Wu 	Zhou on Tue, 13 Dec 2005 14:10:03 +0800 (CST))
Subject: Re: [RFC] GDB patches for hw watchpoints - revised
Reply-to: Eli Zaretskii <eliz@gnu.org>
References: <Pine.LNX.4.63.0512061356530.10445@linux.site> <uslt6km76.fsf@gnu.org>  <20051206202848.GA9568@nevyn.them.org> <Pine.LNX.4.63.0512091013040.18692@linux.site>  <20051209050132.GA5325@nevyn.them.org> <Pine.LNX.4.63.0512101243500.21855@linux.site>  <20051210044752.GA30979@nevyn.them.org> <Pine.LNX.4.63.0512131318090.30718@linux.site>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2005-12/txt/msg00217.txt.bz2

> Date: Tue, 13 Dec 2005 14:10:03 +0800 (CST)
> From: Wu Zhou <woodzltc@cn.ibm.com>
> cc: gdb-patches@sources.redhat.com, mark.kettenis@xs4all.nl, bje@au1.ibm.com,         anton@au1.ibm.com
> 
> 
> 3. The third one is a little tricky.  Now that ppc has at most 1 DABR. So 
> I can set the stopped_data_address to the data address when we set the 
> watchpoint (in ppc_linux_insert_watchpoint).  Everytime 
> target_stopped_data_address is called, the breakpoint is either read or 
> access, so it is already clear that it is stopped by watchpoint.  Then 
> this trick seems to make sense, right?

I think this third method should be good enough for the moment,
assuming that the target system allows only one active watchpoint at a
time.