From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11041 invoked by alias); 12 Oct 2011 08:53:18 -0000 Received: (qmail 11030 invoked by uid 22791); 12 Oct 2011 08:53:16 -0000 X-SWARE-Spam-Status: No, hits=-2.1 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; Wed, 12 Oct 2011 08:52:59 +0000 Received: by vcbfo14 with SMTP id fo14so422414vcb.0 for ; Wed, 12 Oct 2011 01:52:59 -0700 (PDT) Received: by 10.52.100.68 with SMTP id ew4mr22795125vdb.102.1318409578064; Wed, 12 Oct 2011 01:52:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.180.75 with HTTP; Wed, 12 Oct 2011 01:52:38 -0700 (PDT) From: Kevin Pouget Date: Wed, 12 Oct 2011 08:53:00 -0000 Message-ID: Subject: [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/msg00344.txt.bz2 On Mon, Oct 10, 2011 at 9:06 PM, tromey at redhat dot com wrote: > http://sourceware.org/bugzilla/show_bug.cgi?id=12802 >> [...] >> the documentation of gdb.post_event seems not very clear if you don't look at >> what is done internally -- I didn't -- but I think it should be safe to do it >> this way > > Can you suggest how to fix the docs? according to my experimentations, gdb_do_one_event, which (indirectly) triggers the processing of Python events posted with gdb.post_event, is executed right after the prompt has been displayed (and new charactered fed in), and nowhere else (as far as I could investigate). Does it look right to you? Here is the current sentence about when the event will be processed: > This callable will be invoked at some later point, during gdb's event processing. I guess it worth being updated Thanks, Kevin