From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30436 invoked by alias); 23 Nov 2010 23:17:15 -0000 Received: (qmail 30423 invoked by uid 22791); 23 Nov 2010 23:17:14 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 23 Nov 2010 23:17:00 +0000 Received: (qmail 17343 invoked from network); 23 Nov 2010 23:16:58 -0000 Received: from unknown (HELO orlando.localnet) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 23 Nov 2010 23:16:58 -0000 From: Pedro Alves To: gdb-patches@sourceware.org Subject: Re: [patch 2/3] Implement support for PowerPC BookE ranged watchpoints Date: Tue, 23 Nov 2010 23:17:00 -0000 User-Agent: KMail/1.13.5 (Linux/2.6.33-29-realtime; KDE/4.4.5; x86_64; ; ) Cc: Thiago Jung Bauermann , Jan Kratochvil , Joel Brobecker , Eli Zaretskii References: <1290549100.3164.47.camel@hactar> In-Reply-To: <1290549100.3164.47.camel@hactar> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201011232316.56539.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/msg00380.txt.bz2 On Tuesday 23 November 2010 21:51:40, Thiago Jung Bauermann wrote: > Ok? Apologies for jumping in so late, but, I don't think I understand why does the user need to know that a watchpoint is "ranged" or not. All (low-level) watchpoints are ranged, and what's relevant here is only the width of the range the hardware can watch, but that is already a parameter to the target_insert_watchpoint method. So I guess my question is, why can't the target backend manage whether to use a range or "normal" watchpoint when asked to inserted a watchpoint? Is it the watch resource accounting done by breakpoint.c (which is known to be something that should just go away)? -- Pedro Alves