Re: [RFC][patch 3/9] export hooks mechanism to Python

Tom Tromey
2008-04-29T20:07:53Z

>>>>> "Thiago" == Thiago Jung Bauermann <bauerman@br.ibm.com> writes:

>> 2008-04-29 Tom Tromey <tromey@redhat.com>
>> * interps.c (interp_set): Don't call clear_interpreter_hooks.
>> [Temporary hack].

This is one particular thing I wanted to highlight and ask for help on.

>> + /* FIXME - we don't want python to be a normal interpreter, but we
>> + do want to be able to hook in everywhere. Not sure what to do
>> + about this -- maybe allow events to be delivered to multiple
>> + handlers. */
>> +/* clear_interpreter_hooks (); */

The Python code installs hooks so that users can write Python that
reacts to gdb events. I wasn't sure what would be an acceptable
approach here, and for the short term I just disabled this code. But,
this is not a good solution.

A lot of this stuff is marked deprecated. Why is that? Is there some
other approach the Python code should use instead?

Tom