This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch 2/3] Implement support for PowerPC BookE ranged watchpoints
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Cc: Thiago Jung Bauermann <bauerman at br dot ibm dot com>, Jan Kratochvil <jan dot kratochvil at redhat dot com>, Joel Brobecker <brobecker at adacore dot com>, Eli Zaretskii <eliz at gnu dot org>
- Date: Tue, 23 Nov 2010 23:16:56 +0000
- Subject: Re: [patch 2/3] Implement support for PowerPC BookE ranged watchpoints
- References: <1290549100.3164.47.camel@hactar>
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