This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Add an evaluation function hook to Python breakpoints.
- From: Tom Tromey <tromey at redhat dot com>
- To: Doug Evans <dje at google dot com>
- Cc: pmuldoon at redhat dot com, gdb-patches at sourceware dot org
- Date: Wed, 05 Jan 2011 11:35:12 -0700
- Subject: Re: [patch] Add an evaluation function hook to Python breakpoints.
- References: <m38vztlr2r.fsf@redhat.com> <AANLkTimS_32d+7phemj95qCSdJzgXXOxjMhbt_9+i8D6@mail.gmail.com> <m34oags1q1.fsf@fleche.redhat.com> <AANLkTimVN=3CKL2VmKWERSmGxiMA7wDv7pMrSQZc1DMO@mail.gmail.com> <m3ipyulpop.fsf@fleche.redhat.com> <AANLkTim_wXWA2OX1GdZ_rFVwBAr+YjO+B5SSVUN_g0vK@mail.gmail.com> <m3fwtq51zj.fsf@fleche.redhat.com> <AANLkTikk03p4m+s0k+UD8RRVy8YL7wYZsLhy2GNc6d8q@mail.gmail.com> <m31v594w65.fsf@fleche.redhat.com> <AANLkTi=b7=b6FZLjLBCZAqcwaAMnYVTTqTB1Z3dOHSd1@mail.gmail.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