GNU bug report logs - #28630
27.0.50; C-g while a non-main thread is sitting crashes Emacs

Previous Next

Package: emacs;

Reported by: Alex <agrambot <at> gmail.com>

Date: Thu, 28 Sep 2017 07:24:01 UTC

Severity: normal

Found in version 27.0.50

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

Bug is archived. No further changes may be made.

Full log


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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Alex <agrambot <at> gmail.com>
Cc: 28630 <at> debbugs.gnu.org, tom <at> tromey.com
Subject: Re: bug#28630: 27.0.50;
 C-g while a non-main thread is sitting crashes Emacs
Date: Sun, 01 Oct 2017 21:32:22 +0300
> From: Alex <agrambot <at> gmail.com>
> Cc: 28630 <at> debbugs.gnu.org,  tom <at> tromey.com
> Date: Sun, 01 Oct 2017 12:10:40 -0600
> 
> >> Should this be labelled a blocker for Emacs 26?
> >
> > Maybe I'm not sure.  It doesn't sound like threads are used much, if
> > at all, which would make blocking on it silly.
> 
> It's understandable that bug 25214 isn't a blocker for this reason, but
> I think crashing is severe enough to be a blocker, especially since it's
> somewhat trivial to trigger.

If this trigger never happens in real life, why should we block on it?

More generally, if no one besides my sorry self is interested in using
this feature, let alone fixing its bugs, maybe we should simply remove
it from Emacs.

> > Is your Emacs built with --enable-checking?  Because I get an
> > assertion violation in that case, not a crash.
> 
> I just tried building with "./configure --enable-checking" and it still
> crashes for me.

Strange, that's not what I see.

I hope to have some time soon to look into this.  I think I understand
the root cause: we are longjmp-ing in a thread other than the one
which called setjmp.




This bug report was last modified 7 years and 284 days ago.

Previous Next


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