From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id Bu2nNIcJJ2FiGgAAWB0awg (envelope-from ) for ; Wed, 25 Aug 2021 23:24:55 -0400 Received: by simark.ca (Postfix, from userid 112) id C5A111EE1B; Wed, 25 Aug 2021 23:24:55 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id EFDFB1E813 for ; Wed, 25 Aug 2021 23:24:54 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 875D03858D34 for ; Thu, 26 Aug 2021 03:24:54 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 875D03858D34 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1629948294; bh=pfESzJ5/b5sSRSj3pG33zvOSAi4FAI9WOuGRuUDCbDQ=; h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=M+z5XCou1UQXhkxyPH4K32qRO2Ln+T1HtEARfSH/dxmWrCVUoenb4Bt/CoO+6Llhj stqXCWQb3xUCCvpn/ExX+Ovt5cmwEg58D+FKs9D6euXvH2U8e2Nr35kdFCK7dJCIWk mptxRN21/drZ7Li0BXoTX2uYxXyHPZ/UHr7ls8VM= Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by sourceware.org (Postfix) with ESMTPS id 5093F3858D34 for ; Thu, 26 Aug 2021 03:24:26 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 5093F3858D34 Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id 17Q3OAat008506 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 25 Aug 2021 23:24:14 -0400 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.polymtl.ca 17Q3OAat008506 Received: from [10.0.0.11] (192-222-157-6.qc.cable.ebox.net [192.222.157.6]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id CD76E1E813; Wed, 25 Aug 2021 23:24:09 -0400 (EDT) Subject: Re: [PATCH] Add a timeout parameter to gdb_do_one_event To: Patrick Monnerat , gdb-patches@sourceware.org References: <20210823182359.104456-1-patrick@monnerat.net> Message-ID: <4e3085bb-af40-e0dc-73aa-991f97243e06@polymtl.ca> Date: Wed, 25 Aug 2021 23:24:09 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: <20210823182359.104456-1-patrick@monnerat.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Poly-FromMTA: (simark.ca [158.69.221.121]) at Thu, 26 Aug 2021 03:24:10 +0000 X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Simon Marchi via Gdb-patches Reply-To: Simon Marchi Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On 2021-08-23 2:23 p.m., Patrick Monnerat via Gdb-patches wrote: > Since commit b2d8657, having a per-interpreter event/command loop is not > possible anymore. > > As Insight uses a GUI that has its own event loop, gdb and GUI event > loops have then to be "merged" (i.e.: work together). But this is > problematic as gdb_do_one_event is not aware of this alternate event > loop and thus may wait forever. > > The solution is to implement a wait timeout to gdb_do_one_event. This > cannot be done externally as timers are event sources themselves. > > The new parameter defaults to "no timeout": as it is used by Insight > only, there is no need to update calls from the gdb source tree. So, Insight's main loop looks like: while True: call gdb_do_one_event with a timeout call gui_do_one_event with a timeout ? > --- > gdbsupport/event-loop.cc | 45 ++++++++++++++++++++++++++++------------ > gdbsupport/event-loop.h | 2 +- > 2 files changed, 33 insertions(+), 14 deletions(-) > > diff --git a/gdbsupport/event-loop.cc b/gdbsupport/event-loop.cc > index 98d1ada52cd..72c64dcdb72 100644 > --- a/gdbsupport/event-loop.cc > +++ b/gdbsupport/event-loop.cc > @@ -177,16 +177,21 @@ static int update_wait_timeout (void); > static int poll_timers (void); > > /* Process one high level event. If nothing is ready at this time, > - wait for something to happen (via gdb_wait_for_event), then process > - it. Returns >0 if something was done otherwise returns <0 (this > - can happen if there are no event sources to wait for). */ > + wait at most mstimeout milliseconds for something to happen (via mstimeout -> MSTIMEOUT > + gdb_wait_for_event), then process it. Returns >0 if something was > + done, <0 if there are no event sources to wait for, =0 if timeout occurred. > + Setting the timeout to a negative value disables it. Does setting the timeout to 0 mean return immediately if nothing is available? > + The timeout is never used by gdb itself, it is however needed to > + integrate gdb event handling within some external (i.e.: GUI) event > + loop. */ Err, you can probably say "Insight" here. It's not like we want to support programs doing this in general. We make an exception for Insight because of historical reasons, I suppose. > int > -gdb_do_one_event (void) > +gdb_do_one_event (int mstimeout) > { > static int event_source_head = 0; > const int number_of_sources = 3; > int current = 0; > + int res = 0; > > /* First let's see if there are any asynchronous signal handlers > that are ready. These would be the result of invoking any of the > @@ -198,8 +203,6 @@ gdb_do_one_event (void) > round-robin fashion. */ > for (current = 0; current < number_of_sources; current++) > { > - int res; > - > switch (event_source_head) > { > case 0: > @@ -232,14 +235,30 @@ gdb_do_one_event (void) > /* Block waiting for a new event. If gdb_wait_for_event returns -1, > we should get out because this means that there are no event > sources left. This will make the event loop stop, and the > - application exit. */ > - > - if (gdb_wait_for_event (1) < 0) > - return -1; > + application exit. > + If a timeout has been given, a new timer is set accordingly > + to abort event wait. It is deleted upon gdb_wait_for_event > + termination and thus should never be triggered. > + When the timeout is reached, events are not monitored again: > + they already have been checked in the loop above. */ > + > + if (mstimeout != 0) > + { > + int timerid = 0; > + > + if (mstimeout > 0) > + timerid = create_timer (mstimeout, > + [] (gdb_client_data timeridp) > + { > + *((int *) timeridp) = 0; > + }, > + &timerid); > + res = gdb_wait_for_event (1); > + if (timerid) > + delete_timer (timerid); Probably not a practical concern, but by creating timers over and over, for a reaaaaaaally long GDB session, the timer id will eventually wrap and create_timer might return 0. I don't know what will happen then. Simon