From: Tom Tromey <tom@tromey.com>
To: Patrick Monnerat via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add a timeout parameter to gdb_do_one_event
Date: Fri, 15 Apr 2022 10:21:39 -0600 [thread overview]
Message-ID: <87a6cm1fn0.fsf@tromey.com> (raw)
In-Reply-To: <20220317130846.162955-1-patrick@monnerat.net> (Patrick Monnerat via Gdb-patches's message of "Thu, 17 Mar 2022 14:08:46 +0100")
>>>>> "Patrick" == Patrick Monnerat via Gdb-patches <gdb-patches@sourceware.org> writes:
Patrick> As Insight uses a GUI that has its own event loop, gdb and GUI event
Patrick> loops have then to be "merged" (i.e.: work together). But this is
Patrick> problematic as gdb_do_one_event is not aware of this alternate event
Patrick> loop and thus may wait forever.
Can Insight fds just be added to the GDB event loop?
Patrick> The solution is to implement a wait timeout to gdb_do_one_event. This
Patrick> cannot be done externally as gdb timers are event sources themselves.
I guess what you're doing is Insight is calling gdb_do_one_event
repeatedly? And you want it to exit with a timeout so you can then run
the Insight event loop?
I don't really know the scenario here so I am just guessing.
Anyway I don't understand why installing your own timer wouldn't work.
It seems to me that if a timer is handled, gdb_do_one_event will return.
Tom
next prev parent reply other threads:[~2022-04-15 16:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 13:08 Patrick Monnerat via Gdb-patches
2022-04-15 16:21 ` Tom Tromey [this message]
2022-04-16 0:38 ` Patrick Monnerat via Gdb-patches
2022-07-22 13:41 ` Simon Marchi via Gdb-patches
2022-07-22 22:45 ` Patrick Monnerat via Gdb-patches
2022-07-25 1:07 ` Simon Marchi via Gdb-patches
2022-08-18 11:16 ` Andrew Burgess via Gdb-patches
2022-08-19 11:29 ` Patrick Monnerat via Gdb-patches
2022-08-23 18:38 ` Tom Tromey
-- strict thread matches above, loose matches on Subject: below --
2022-03-14 14:49 Patrick Monnerat via Gdb-patches
2022-03-14 16:17 ` Pedro Alves
2021-08-26 18:30 Patrick Monnerat via Gdb-patches
2021-08-23 18:23 Patrick Monnerat via Gdb-patches
2021-08-26 3:24 ` Simon Marchi via Gdb-patches
2021-08-26 11:36 ` Patrick Monnerat via Gdb-patches
2021-08-26 13:47 ` Simon Marchi via Gdb-patches
2021-08-26 15:14 ` Patrick Monnerat via Gdb-patches
2021-08-27 18:08 ` Tom Tromey
2021-08-28 0:07 ` Patrick Monnerat via Gdb-patches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6cm1fn0.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox