From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16956 invoked by alias); 14 Jun 2006 01:21:59 -0000 Received: (qmail 16947 invoked by uid 22791); 14 Jun 2006 01:21:59 -0000 X-Spam-Check-By: sourceware.org Received: from ausmtp05.au.ibm.com (HELO ausmtp05.au.ibm.com) (202.81.18.154) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 14 Jun 2006 01:21:57 +0000 Received: from sd0208e0.au.ibm.com (d23rh904.au.ibm.com [202.81.18.202]) by ausmtp05.au.ibm.com (8.13.6/8.13.6) with ESMTP id k5E1OsAa5325004 for ; Wed, 14 Jun 2006 11:24:54 +1000 Received: from d23av04.au.ibm.com (d23av04.au.ibm.com [9.190.250.237]) by sd0208e0.au.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k5E1PAIc216936 for ; Wed, 14 Jun 2006 11:25:10 +1000 Received: from d23av04.au.ibm.com (loopback [127.0.0.1]) by d23av04.au.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k5E1Lmge013822 for ; Wed, 14 Jun 2006 11:21:49 +1000 Received: from [9.181.90.178] ([9.181.90.178]) by d23av04.au.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k5E1Lkmo013765; Wed, 14 Jun 2006 11:21:47 +1000 Date: Wed, 14 Jun 2006 01:21:00 -0000 From: Wu Zhou To: Eli Zaretskii cc: nathan@codesourcery.com, gdb-patches@sourceware.org Subject: Re: adjust watchpoint testing In-Reply-To: Message-ID: References: <4489E0D8.2000702@codesourcery.com> <448D98E7.7030806@codesourcery.com> <448E59AE.50507@codesourcery.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00211.txt.bz2 On Tue, 13 Jun 2006, Eli Zaretskii wrote: > > Date: Tue, 13 Jun 2006 14:43:13 +0800 (CST) > > From: Wu Zhou > > cc: gdb-patches@sourceware.org > > > > Do you mean to hard-wire the number of the hw watchpoint the underlying target > > support into these base board files, or just set the number to 1? > > > > I guess that we might need to work out a way to detect the number > > automatically. Any thought? > > I don't think there's any practical way to detect the number of > supported watchpoints. It depends on the particulars of the watched > regions, and different targets have different peculiarities. For > example, x86 can set an unlimited number of watchpoints provided that > they watch the same address and length. What about adding a gdbarch specific member function to do this? If this is still target dependent, we can overwrite it in the relevant tdep file. For x86 case, maybe we can take them as only one watchpoint if they are watching on the same address of same length? My very initial idea though. Feel free to correct me if I am wrong. Thanks - Wu Zhou