From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 615 invoked by alias); 18 Oct 2011 11:57:28 -0000 Received: (qmail 605 invoked by uid 22791); 18 Oct 2011 11:57:27 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-vx0-f169.google.com (HELO mail-vx0-f169.google.com) (209.85.220.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 18 Oct 2011 11:57:08 +0000 Received: by vcbfk1 with SMTP id fk1so544854vcb.0 for ; Tue, 18 Oct 2011 04:57:08 -0700 (PDT) Received: by 10.52.92.212 with SMTP id co20mr1957823vdb.119.1318939028056; Tue, 18 Oct 2011 04:57:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.180.75 with HTTP; Tue, 18 Oct 2011 04:56:48 -0700 (PDT) In-Reply-To: References: From: Kevin Pouget Date: Tue, 18 Oct 2011 13:32:00 -0000 Message-ID: Subject: Re: [Python - doc] gdb.post_event description To: Tom Tromey Cc: gdb-patches@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes 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: 2011-10/txt/msg00496.txt.bz2 On Fri, Oct 14, 2011 at 9:48 PM, Tom Tromey wrote: >>>>>> "Kevin" == Kevin Pouget writes: > > Kevin> according to my experimentations, gdb_do_one_event, which (indirectly) > Kevin> triggers the processing of Python events posted with gdb.post_event, > Kevin> is executed right after the prompt has been displayed (and new > Kevin> charactered fed in), and nowhere else (as far as I could investigate). > > Kevin> Does it look right to you? > > Yeah, but I would not want to document this too precisely; it is good, I > think, to have some leeway so we can run the event queue at other times > if we find the need in the future. sure, but I think that the notion of "event" is quite vague here, for instance we've got Python events, which are totally unrelated to "post_event" (as far as I understood); and internally there are inferior events. (Actually, with that knowledge, I expected 'post_event' events to be processed more often). So I think it's important to state when the callback will be triggered, give the prompt as an example, and mentioned that more event processing points might be added in the next releases What do you think about it? Thanks, Kevin