GNU bug report logs -
#28472
26.0.50; Deadlock in Fkill_emacs on MS-Windows
Previous Next
Reported by: Richard Copley <rcopley <at> gmail.com>
Date: Sat, 16 Sep 2017 10:32:01 UTC
Severity: normal
Found in version 26.0.50
Done: Stefan Kangas <stefan <at> marxist.se>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> 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.
This bug report was last modified 4 years and 280 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.