From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18451 invoked by alias); 20 Dec 2009 12:33:46 -0000 Received: (qmail 18438 invoked by uid 22791); 20 Dec 2009 12:33:45 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 20 Dec 2009 12:33:42 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 7BE672BAB71; Sun, 20 Dec 2009 07:33:40 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id rj5ILw-1VWFd; Sun, 20 Dec 2009 07:33:40 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id B02642BAB6C; Sun, 20 Dec 2009 07:33:39 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 5DF35F5892; Sun, 20 Dec 2009 13:33:24 +0100 (CET) Date: Sun, 20 Dec 2009 12:33:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: S?rgio Durigan J?nior , gdb-patches@sourceware.org, bauerman@br.ibm.com, luisgpm@linux.vnet.ibm.com, tyrlik@us.ibm.com Subject: Re: [PATCH 0/2] Support the new PPC476 processor Message-ID: <20091220123324.GG2788@adacore.com> References: <200912161847.17162.sergiodj@linux.vnet.ibm.com> <83y6l060qp.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <83y6l060qp.fsf@gnu.org> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-12/txt/msg00279.txt.bz2 > > - Usage example: watch-range &i,&k / awatch-range 0xbffff8e8,0xbffff8f8 / > > rwatch-range 0xbffff8e8,+8 > > Why is there a need for a separate GDB command? What are the > use-cases where the user would want to watch a region that is spanned > by more than one (albeit large) variable? If such use-cases are > infrequent enough or obscure, then we could simply use the normal > watch commands, and support any corner use-cases with something like > > watch *0xbffff8e8@8 FWIW, I actually prefer the seperate command over your suggestion. The use of the @8 seems logical, but '@' is little known and the new command seems more explicit about the actual range being watched. -- Joel