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

[Tom Tromey <tromey@redhat.com>]

>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:

Tom> I think there should also be a test for the case where there is an
Tom> ordinary user breakpoint at the same location as the Python breakpoints.
Tom> In this case, the user breakpoint should stop, but all the Python
Tom> methods should be invoked first.

Phil> All the breakpoints at a location will be evaluated, but does the order
Phil> matter?

The order matters in the sense that GDB can't stop and give the user a
prompt before evaluating all the conditions.

I don't think we should make any promises about the relative order in
which breakpoint conditions will be evaluated.

Phil> I can add the test to prove the point, but the Python breakpoints
Phil> will have the evaluation function called regardless if the user
Phil> breakpoint was first.

Yes, that is what we want to test -- that the condition methods are
evaluated regardless of whether a user breakpoint exists.  This is the
"no interference" case.

Tom