GNU bug report logs - #28472
26.0.50; Deadlock in Fkill_emacs on MS-Windows

Previous Next

Full log

Message #16 received at 28472-done <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: rcopley <at> gmail.com, 28472-done <at> debbugs.gnu.org
Subject: Re: bug#28472: 26.0.50; Deadlock in Fkill_emacs on MS-Windows
Date: Mon, 10 Aug 2020 09:47:30 -0700

Eli Zaretskii <eliz <at> gnu.org> writes:

>> Date: Sat, 16 Sep 2017 14:15:51 +0300
>> From: Eli Zaretskii <eliz <at> gnu.org>
>> Cc: 28472 <at> debbugs.gnu.org
>>
>> Thanks.  I see nothing in this backtrace that could tell what to do to
>> avoid the hang.  All the threads are stuck in system calls, two of
>> then in WaitForSingleObject.  So it sounds like some race condition,
>> but I have no idea what that could be.  FWIW, it never happened to me
>> during a bootstrap.
>>
>> It could be bug#14333, which we never solved.  But the backtraces
>> there were more informative.
>
> One possible way to gain more info is to add printf's in several
> places in term_timers and in term_ntproc, and see what this tells us
> about where Emacs gets stuck.  But make sure bootstrap commands don't
> redirect stdout/stderr to some place, or you may not see the output.

No more information was given within 2 years, 46 weeks. Since the
backtrace was not enough to make any progress, I'm closing this bug now.

If this is still an issue, please reply to this email (use "Reply to
all" in your email client) and we can reopen the bug report.

Best regards,
Stefan Kangas

Previous Next

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