From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16127 invoked by alias); 7 Oct 2002 05:53:14 -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 16119 invoked from network); 7 Oct 2002 05:53:12 -0000 Received: from unknown (HELO is.elta.co.il) (199.203.121.2) by sources.redhat.com with SMTP; 7 Oct 2002 05:53:12 -0000 Received: from is (is [199.203.121.2]) by is.elta.co.il (8.9.3/8.8.8) with SMTP id HAA06710; Mon, 7 Oct 2002 07:53:26 +0200 (IST) Date: Sun, 06 Oct 2002 22:53:00 -0000 From: Eli Zaretskii X-Sender: eliz@is To: Klee Dienes cc: gdb-patches@sources.redhat.com Subject: Re: [PATCH] Compare contents when evaluating an array watchpoint In-Reply-To: <51EACEDC-D90C-11D6-9330-00039396EEB8@apple.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-10/txt/msg00168.txt.bz2 On Sun, 6 Oct 2002, Klee Dienes wrote: > The following patch allows one to set watchpoints on arrays, and have > the watchpoint triggered if any element in the array changes. Without > the patch, the C value_equal semantics causes the address of the array > to be checked for change, not the contents --- resulting in a > watchpoint that can never be hit. > > This is particularly useful if one wants to do commands like watch > {char[80]} 0xfff0000, or similar, in order to watch an arbitrary region > of memory. What will this do to hardware watchpoints on arrays/array elements? On many platforms, hardware watchpoints have size limitations, so large arrays cannot be watched in their entirety.