From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18381 invoked by alias); 14 Mar 2013 09:43:32 -0000 Received: (qmail 18371 invoked by uid 22791); 14 Mar 2013 09:43:31 -0000 X-SWARE-Spam-Status: No, hits=-8.1 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_SPAMHAUS_DROP,KHOP_THREADED,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 14 Mar 2013 09:43:27 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r2E9hP1I020308 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 14 Mar 2013 05:43:25 -0400 Received: from localhost.localdomain (ovpn-116-26.ams2.redhat.com [10.36.116.26]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id r2E9hOGR025481; Thu, 14 Mar 2013 05:43:25 -0400 Message-ID: <51419BBB.1030800@redhat.com> Date: Thu, 14 Mar 2013 09:43:00 -0000 From: Phil Muldoon MIME-Version: 1.0 To: Gareth McMullin CC: gdb@sourceware.org Subject: Re: Exposing inferior_created in Python References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2013-03/txt/msg00013.txt.bz2 On 14/03/13 04:18, Gareth McMullin wrote: > Hi > > I'm interested in having the inferior_created observer exposed as a > Python event I think it is fine to create event and observers in GDB/Python that you have identified a need for. That being said, what do you mean by inferior_created event? Currently we have observers in the Python API for: * Breakpoint events * Continue events. * Exiting events * New object file events * Signal events * Inferior halting/stopping events * Thread events Would the thread event/observer satisfy your use-case? I am pretty much guessing, though, until you can expand on the inferior_created case. Cheers Phil