This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA 2/3] Demote to sw watchpoint only in update_watchpoint
- 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, uweigand at de dot ibm dot com
- Date: Tue, 03 May 2011 19:55:53 +0300
- Subject: Re: [RFA 2/3] Demote to sw watchpoint only in update_watchpoint
- References: <201104291726.p3THQVaC029608@d06av02.portsmouth.uk.ibm.com> <1304398546.2245.80.camel@hactar> <E1QH8jn-0001Wm-64@fencepost.gnu.org> <201105031058.44489.pedro@codesourcery.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Tue, 3 May 2011 10:58:44 +0100
> Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
> uweigand@de.ibm.com
>
> What if we tried to make GDB do that instead? (try inserting
> watchpoint immediately, instead of trying to do any sort of
> accounting.)
That could work, but won't it get us in trouble, e.g., when there are
other threads running? They could inadvertently hit those watchpoints
while we are trying to insert them, no?
Or we could let targets which needs that (e.g., those using jtag as
you described) try inserting the watchpoints to respond to GDB's
request in target_can_use_hardware_watchpoint. Other targets, which
can decide that without inserting, would not need to do that.
WDYT?