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

[Doug Evans]

On Tue, Dec 21, 2010 at 12:01 PM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Doug" == Doug Evans <dje@google.com> writes:
>
> Doug> For example, what happens after a checker employing stop_p says
> Doug> "stop"?  There's nothing more in the API that helps the user know
> Doug> *why* the checker said "stop".  At the moment the API doesn't provide
> Doug> anything.  Checkers will have to print an error message, but I have a
> Doug> feeling something more will be useful.
> Doug> [Did you have something in mind, or am I missing something?]
>
> The method in question is attached to a particular breakpoint.  So, if
> it requests a stop, it will be reported as coming from that breakpoint.

That feels a bit subtle (and easy for the user to confuse with a
normal breakpoint).
[e.g. as compared to getting a SIGSEGV]

Plus will it also breakdown if a developer sets his/her own breakpoint
at that location?