From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29042 invoked by alias); 13 Jun 2006 06:12:40 -0000 Received: (qmail 29033 invoked by uid 22791); 13 Jun 2006 06:12:39 -0000 X-Spam-Check-By: sourceware.org Received: from ausmtp04.au.ibm.com (HELO ausmtp04.au.ibm.com) (202.81.18.152) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 13 Jun 2006 06:12:37 +0000 Received: from sd0208e0.au.ibm.com (d23rh904.au.ibm.com [202.81.18.202]) by ausmtp04.au.ibm.com (8.13.6/8.13.5) with ESMTP id k5D6G7PA173336 for ; Tue, 13 Jun 2006 16:16:07 +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 k5D6FscJ211264 for ; Tue, 13 Jun 2006 16:15:54 +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 k5D6CVOJ011069 for ; Tue, 13 Jun 2006 16:12:31 +1000 Received: from [9.181.133.20] ([9.181.133.20]) by d23av04.au.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k5D6CT3Y010875; Tue, 13 Jun 2006 16:12:30 +1000 Date: Tue, 13 Jun 2006 06:12:00 -0000 From: Wu Zhou To: Nathan Sidwell cc: gdb-patches@sourceware.org Subject: Re: adjust watchpoint testing In-Reply-To: <448D98E7.7030806@codesourcery.com> Message-ID: References: <4489E0D8.2000702@codesourcery.com> <448D98E7.7030806@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/msg00167.txt.bz2 Nathan, I see your code have such two lines: + if [target_info exists gdb,hardware_watchpoints] { + set nwatch [target_info gdb,hardware_watchpoints] Where is this target_info variable set up? Did you set that somewhere in the dejagnu package? I am very curious about how it is implemented. I am now using a test and trial method. If rwatch command reports that this type of hw watchpoint is not supported, then I will assume this target don't support hardware watchpoint; if it replys with a message "Hardware read watchpoint...", then I assume it is supported. But I don't figure out how to get precisely how many hw watchpoints the target support? How did you make that? Can you share your idea with me? Thanks a lot! Regards - Wu Zhou On Mon, 12 Jun 2006, Nathan Sidwell wrote: > Wu Zhou wrote: > > Nathan, > > > > I had similar concerns about these watchpoint tests with you. However, I'd > > like to propose a somewhat different solution. > > > This target-dependent feature might incur confusion some where. One may > > have difficulty in knowing for sure what this case is trying to test: s/w > > watchpoint, or h/w watchpoint, or both? If there are errors reported, what > > type of watchpoint trigger that? To track into the root cause, which code > > to look at? > > To clarify the situation, I propose to let recurse.exp based on totally on > > software simulated watchpoint. This can be done easily, by using "set > > can-use-hardware-watchpoint 0". > > Thanks for your comments. Over the weekend, I had a thought that the problem > is the remote stub not telling gdb how many watchpoints it can support. I > think this is a thing for qPacketInfo to deal with, and I can talk to Dan > about that. > > nathan > -- > Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery > nathan@codesourcery.com :: http://www.planetfall.pwp.blueyonder.co.uk > >