This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC][patch 3/9] export hooks mechanism to Python
- From: Tom Tromey <tromey at redhat dot com>
- To: Thiago Jung Bauermann <bauerman at br dot ibm dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 29 Apr 2008 14:07:21 -0600
- Subject: Re: [RFC][patch 3/9] export hooks mechanism to Python
- References: <20080429155212.444237503@br.ibm.com> <20080429155304.641779989@br.ibm.com>
- Reply-to: tromey at redhat dot com
>>>>> "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