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

[Tom Tromey <tromey at redhat dot com>]

>>>>> "Doug" == Doug Evans <dje@google.com> writes:

Doug> The user will see the normal breakpoint output, and then be expected
Doug> to know that the breakpoint is special (e.g., a rule was violated and
Doug> that s/he needs to pay attention to what the rule was).  Is there a
Doug> plan to have something more?  [Or am I missing something?]

Yeah, we want to expose some of the breakpoint_ops stuff to python.

Doug> Sorry, maybe I was too subtle.
Doug> If one is using this facility to implement a rule checker that stops
Doug> when the rule is violated, and one sets another breakpoint at the same
Doug> location, when the program stops how does one know whether the rule
Doug> was violated or not?

One does not.  This is a pre-existing problem in gdb.


Phil, let's withdraw this patch until some later time when we have
worked out the issues.  We can continue to discuss on the archer list.

I think we should at least deal with exposing to Python the bits needed
to customize breakpoint notifications.

Also we should write a couple real-life uses of this to make sure it is
working ok.  At least we should update the glibc heap stuff to use it;
and if other bits are done in time we can either look at the mutex
tracker (requires Sergio's work) or return breakpoints (I think this
requires Sami's work).

Tom