From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9335 invoked by alias); 30 Apr 2008 19:58:52 -0000 Received: (qmail 9319 invoked by uid 22791); 30 Apr 2008 19:58: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; Wed, 30 Apr 2008 19:58: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 m3UJwVGv015953; Wed, 30 Apr 2008 15:58:31 -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 m3UJwUPx015609; Wed, 30 Apr 2008 15:58:30 -0400 Received: from opsy.redhat.com (vpn-248-74.boston.redhat.com [10.13.248.74]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m3UJwT8S024882; Wed, 30 Apr 2008 15:58:30 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 4548A508471; Wed, 30 Apr 2008 13:58:29 -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> <20080430162841.GA3427@caradoc.them.org> From: Tom Tromey Reply-To: Tom Tromey X-Attribution: Tom Date: Wed, 30 Apr 2008 23:00:00 -0000 In-Reply-To: <20080430162841.GA3427@caradoc.them.org> (Daniel Jacobowitz's message of "Wed\, 30 Apr 2008 12\:28\:41 -0400") 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/msg00716.txt.bz2 >>>>> "Daniel" == Daniel Jacobowitz writes: Daniel> What sort of events are you hooking usefully? Can we share e.g. the Daniel> CLI "hook-" mechanism? A lot of this code is just speculative -- based on the idea that it would be nice to be able to write Python scripts which do things reactively; say for instance take some action after an "attach". (A lot of this has never even been tried.) However internally the Python code uses events to track breakpoint creation and destruction. I suppose I could try to add new observers to let me do that. Tom