Re: [patch] Add an evaluation function hook to Python breakpoints.

[Phil Muldoon <pmuldoon at redhat dot com>]

Phil Muldoon <pmuldoon@redhat.com> writes:

> In the case of a new style breakpoint having both a CLI .condition() AND
> an implemented method (though I could never see why you would want to do
> this), whichever of those methods told GDB not to stop would trump the
> other. (GDB assumes in bpstat_stop_status that the breakpoint will stop
> the inferior (other than special cases like moribund breakpoints) and it
> is up to the breakpoint evaluation to say, "hey don't stop".  So the
> stop-bit is never set by the conditional stuff, just unset).

Reading back this sounds bogus.  We've never had a situation where you
can have two conditions determining the stop status of one breakpoint.  In
that case I think the inverse is true, if one says "stop" it should
trump the other.  In that case, and if that is the chosen path, I'll
have to rewire a few extra things.

Cheers

Phil