From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29792 invoked by alias); 23 Jun 2008 17:27:32 -0000 Received: (qmail 29784 invoked by uid 22791); 23 Jun 2008 17:27:32 -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; Mon, 23 Jun 2008 17:27:14 +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 m5NHQoPD008769; Mon, 23 Jun 2008 13:26:50 -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 m5NHQoRl025324; Mon, 23 Jun 2008 13:26:50 -0400 Received: from opsy.redhat.com (vpn-10-3.bos.redhat.com [10.16.10.3]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m5NHQnCS029897; Mon, 23 Jun 2008 13:26:50 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 6AD81378157; Mon, 23 Jun 2008 11:26:49 -0600 (MDT) To: Joel Brobecker Cc: Thiago Jung Bauermann , Daniel Jacobowitz , gdb-patches@sourceware.org Subject: Re: [RFC][patch 3/9] export hooks mechanism to Python References: <20080615183110.xi9zc6qx2iokwwsg@imap.linux.ibm.com> <20080616014219.GA9913@caradoc.them.org> <20080617121342.k0o647casks4w4c4@imap.linux.ibm.com> <20080617203741.GA3711@adacore.com> From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom Date: Mon, 23 Jun 2008 17:58:00 -0000 In-Reply-To: <20080617203741.GA3711@adacore.com> (Joel Brobecker's message of "Tue\, 17 Jun 2008 16\:37\: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-06/txt/msg00390.txt.bz2 >>>>> "Joel" == Joel Brobecker writes: >> Observers look like a useful feature in GDB to be used by scripts, >> IMHO we should think about ways to make it available to python, and consider >> turning it into a stable exported interface... Joel> Exposing some events to Python sounds pretty reasonable, but I also Joel> prefer if we did not expose the observers directly, for the reasons Joel> that Daniel explained. The event at the Python would be very well Joel> defined and (hopefully) stable while we are free to modify the observers. FWIW we talked about this at the Summit and my understanding is that we agreed there should be some "buffering" between raw observers and Python code. BTW, Thiago, this patch is a bit obsolete since I moved breakpoint observer registration directly into python/breakpoint.c. Tom