[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#25172: 26.0.50; Concurrency feature, sit-for doesn't work (crashing

From: Elias Mårtenson
Subject: bug#25172: 26.0.50; Concurrency feature, sit-for doesn't work (crashing and unexpected behaviour)
Date: Wed, 14 Dec 2016 10:58:36 +0800

On 14 December 2016 at 00:26, Eli Zaretskii <address@hidden> wrote:
> From: Elias Mårtenson <address@hidden>
> Date: Tue, 13 Dec 2016 12:16:41 +0800
> Cc: Clément Pit--Claudel <address@hidden>,
>       address@hidden
> This is the output from the SIGABRT case. Again, there is a lot of information before the actual "bt full" output:

This shows exactly the situation which I imagined could happen: 3
threads, including the main thread, all running the code in xg_select
which calls unblock_input, and aborting due to the block level being

Can you try removing the calls to block_input/unblock_input from
xgselect.c, and see if these crashes then stop?

I have tried this now, and it's much more stable now. It doesn't immediately crash, and sometimes it doesn't crash at all.

When it crashes, it does so after several seconds, and I have captured two of these crashes.

I will post these backtraces in the following two emails.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]