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] Add an evaluation function hook to Python breakpoints.


> From: Phil Muldoon <pmuldoon@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Mon, 13 Dec 2010 17:20:57 +0000
> 
> > So I would rephrase the text in question like this:
> >
> >   If this function is defined in a sub-class of @code{gdb.Breakpoint},
> >   it will be called when the inferior reaches any breakpoint which
> >   instantiates that sub-class.
> 
> But only if the inferior has stopped at the location of that
> breakpoint.

That's why my suggested text says "when the inferior reaches any
breakpoint".  I thought it was clear that "reaching a breakpoint"
means to get to the breakpoint's location.  And when the inferior
reaches the breakpoint's location, it inevitably stops, right?

I don't mind making this more explicit, either:

  If this function is defined in a sub-class of @code{gdb.Breakpoint},
  it will be called when the inferior stops at any location of a
  breakpoint which instantiates that sub-class.


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