GNU bug report logs - #25247
26.0.50; Concurrency crashes

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: lokedhs <at> gmail.com
Cc: raeburn <at> raeburn.org, 25247 <at> debbugs.gnu.org, tino.calancha <at> gmail.com
Subject: bug#25247: 26.0.50; Concurrency crashes with XLib
Date: Fri, 30 Dec 2016 22:40:47 +0200

> Date: Fri, 30 Dec 2016 20:54:25 +0200
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: raeburn <at> raeburn.org, tino.calancha <at> gmail.com, 25247 <at> debbugs.gnu.org
> 
> I think the results are unexpected only because you think of the
> threads as running in parallel.  But they don't; only one thread runs
> at any given time, the rest are stuck, either in 'pselect', waiting
> for some input or time-out, or waiting for the global lock to become
> available.  And sleep-for yields to other threads (i.e. makes the
> global lock available).

And one additional piece of this puzzle is that you only see stuff
inserted into a buffer when redisplay runs.  And redisplay runs when
some thread waits for input and finds that none is available.

Previous Next

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