From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23598 invoked by alias); 27 Jul 2010 16:30:14 -0000 Received: (qmail 23587 invoked by uid 22791); 27 Jul 2010 16:30:12 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 27 Jul 2010 16:30:07 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id B596A2BABDB; Tue, 27 Jul 2010 12:30:05 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id mxUGCmUJctfo; Tue, 27 Jul 2010 12:30:05 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 83B002BAB47; Tue, 27 Jul 2010 12:30:05 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id B5FD9F58FA; Tue, 27 Jul 2010 09:29:56 -0700 (PDT) Date: Tue, 27 Jul 2010 16:30:00 -0000 From: Joel Brobecker To: Phil Muldoon Cc: gdb-patches ml Subject: Re: [patch] Implement post_event for Python scripts. Message-ID: <20100727162956.GG13267@adacore.com> References: <4C45F0B0.5000903@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C45F0B0.5000903@redhat.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2010-07/txt/msg00433.txt.bz2 > +@findex gdb.post_event > +@defun post_event event > +Put @var{event}, a callable object taking no arguments, into > +@value{GDBN}'s internal event queue. This callable will be invoked at > +some later point, during @value{GDBN}'s event processing. Events > +posted using @code{post_event} will be run in the order in which they > +were posted; however, there is no way to know when they will be > +processed relative to other events inside @value{GDBN}. Would it be useful to provide an exemple of how this feature could be used? It does not seem obvious, and I am not sure without reading the GDB Manual that users are familiar with GDB's internal even queue... -- Joel