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: Eli Zaretskii <eliz at gnu dot org>
- To: Pedro Alves <pedro at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org, bauerman at br dot ibm dot com, jan dot kratochvil at redhat dot com, brobecker at adacore dot com
- Date: Fri, 24 Dec 2010 13:25:54 +0200
- Subject: Re: [patch 2/3] Implement support for PowerPC BookE ranged watchpoints
- References: <1290549100.3164.47.camel@hactar> <201011271747.39053.pedro@codesourcery.com> <1293130182.14239.21.camel@hactar> <201012232017.11120.pedro@codesourcery.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Thu, 23 Dec 2010 20:16:45 +0000
> Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
> Jan Kratochvil <jan.kratochvil@redhat.com>,
> Joel Brobecker <brobecker@adacore.com>,
> Eli Zaretskii <eliz@gnu.org>
>
> The resource accounting bits, I still say that they should all just
> go away (at some point), and gdb should just try to insert the
> watchpoint immediately, and see if the target refuses.
I agree -- assuming, that is, that all the targets we support that can
do hardware watchpoints allow us to insert the watchpoints separately
from resuming the debuggee. If there are targets that actually insert
the watchpoints as part as resuming the debuggee, those targets will
be unable to tell us anything useful about the watchpoint resources
until we actually resume the debuggee. For those targets, we will
need to have some resource accounting in GDB, to give the user
reasonable feedback about resource over-booking.