GNU bug report logs - #25214
26.0.50; Interacting with user from threads other than the primary

Previous Next

Full log

Message #61 received at 25214 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Zhang Haijun <ccsmile2008 <at> outlook.com>
Cc: 25214 <at> debbugs.gnu.org
Subject: Re: bug#25214: #25214 26.0.50; Interacting with user from threads
 other than the primary
Date: Thu, 07 Feb 2019 19:25:51 +0200

> From: Zhang Haijun <ccsmile2008 <at> outlook.com>
> CC: "25214 <at> debbugs.gnu.org" <25214 <at> debbugs.gnu.org>
> Date: Thu, 7 Feb 2019 14:56:22 +0000
> 
> 
> Sorry for my poor English and poor expression. I mean a data channel, for example a pair of fd created by pipe() or a pair of sockets created by socketpair(). producer-consumer model.
> 
> > If another thread writes to some fd, it means the main thread is not
> > running, so it cannot receive the event, even if we did find the way
> > of having an fd which can be read by one thread and written by all the
> > others.
> 
> Another thread send a input request and then be blocked on a lock(for example, keybord lock, one lock per thread). The main thread(or keybord sheduler thread) then can wake up one thread and give keybord to it.

Unless the thread that listens to these requests is never blocked, I
don't see how this could work.

And in any case, what should a non-main thread do if it wants to ask a
question?  Asking a question involves displaying the question before
reading the answer.  You only talked about the second part.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.