This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch 2/3] Implement support for PowerPC BookE ranged watchpoints


On Fri, 2010-12-24 at 13:25 +0200, Eli Zaretskii wrote:
> > 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.

AFAIK breakpoint.c would have to be changed to distinguish between
software breakpoints/watchpoints and hardware breakpoints/watchpoints,
and install the latter at the moment the user creates it, and the former
would continue to be installed at the time GDB resumes the inferior, as
breakpoint.c works now.
-- 
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]