From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27771 invoked by alias); 26 Nov 2010 11:09:29 -0000 Received: (qmail 27760 invoked by uid 22791); 26 Nov 2010 11:09:28 -0000 X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout21.012.net.il (HELO mtaout21.012.net.il) (80.179.55.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 26 Nov 2010 11:09:23 +0000 Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0LCH00I00O8ES200@a-mtaout21.012.net.il> for gdb-patches@sourceware.org; Fri, 26 Nov 2010 13:08:53 +0200 (IST) Received: from HOME-C4E4A596F7 ([84.229.63.39]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LCH00IXHOARIZ80@a-mtaout21.012.net.il>; Fri, 26 Nov 2010 13:08:53 +0200 (IST) Date: Fri, 26 Nov 2010 11:09:00 -0000 From: Eli Zaretskii Subject: Re: [patch 2/3] Implement support for PowerPC BookE ranged watchpoints In-reply-to: <201011251731.58135.pedro@codesourcery.com> To: Pedro Alves Cc: bauerman@br.ibm.com, gdb-patches@sourceware.org, jan.kratochvil@redhat.com, brobecker@adacore.com Reply-to: Eli Zaretskii Message-id: <83k4k07324.fsf@gnu.org> References: <1290549100.3164.47.camel@hactar> <201011232316.56539.pedro@codesourcery.com> <1290632755.3164.94.camel@hactar> <201011251731.58135.pedro@codesourcery.com> X-IsSubscribed: yes 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: 2010-11/txt/msg00450.txt.bz2 > From: Pedro Alves > Date: Thu, 25 Nov 2010 17:31:57 +0000 > Cc: gdb-patches@sourceware.org, > Jan Kratochvil , > Joel Brobecker , > Eli Zaretskii > > > So that's way I created a target_insert_ranged_watchpoint. The other > > option would be to add a flag to target_insert_watchpoint... > > It appears to me that if there should be a new kind of way to > insert watchpoints, it should be to allow setting watchpoints > that only work if the accesses are aligned What would be the use-cases where such behavior would be needed?