From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32572 invoked by alias); 29 Apr 2008 20:07:53 -0000 Received: (qmail 32530 invoked by uid 22791); 29 Apr 2008 20:07:52 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 29 Apr 2008 20:07:34 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m3TK7No1008571; Tue, 29 Apr 2008 16:07:23 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m3TK7MNG020861; Tue, 29 Apr 2008 16:07:22 -0400 Received: from opsy.redhat.com (vpn-248-24.boston.redhat.com [10.13.248.24]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m3TK7MIB003706; Tue, 29 Apr 2008 16:07:22 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id BA529508248; Tue, 29 Apr 2008 14:07:21 -0600 (MDT) To: Thiago Jung Bauermann Cc: gdb-patches@sourceware.org Subject: Re: [RFC][patch 3/9] export hooks mechanism to Python References: <20080429155212.444237503@br.ibm.com> <20080429155304.641779989@br.ibm.com> From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom Date: Tue, 29 Apr 2008 21:29:00 -0000 In-Reply-To: <20080429155304.641779989@br.ibm.com> (Thiago Jung Bauermann's message of "Tue\, 29 Apr 2008 12\:52\:15 -0300") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-04/txt/msg00674.txt.bz2 >>>>> "Thiago" == Thiago Jung Bauermann writes: >> 2008-04-29 Tom Tromey >> * 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