GNU bug report logs - #32502
27.0.50; Tramp; C-g during asynchronous remote find-file kills Emacs

Previous Next

Package: emacs;

Reported by: Gemini Lasswell <gazally <at> runbox.com>

Date: Wed, 22 Aug 2018 18:26:02 UTC

Severity: normal

Tags: fixed

Found in version 27.0.50

Fixed in version 27.1

Done: Michael Albinus <michael.albinus <at> gmx.de>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: gazally <at> runbox.com, 32502 <at> debbugs.gnu.org
Subject: bug#32502: 27.0.50; Tramp; C-g during asynchronous remote find-file kills Emacs
Date: Wed, 29 Aug 2018 18:46:01 +0200
Eli Zaretskii <eliz <at> gnu.org> writes:

>> > Emacs aborting in this case is arguably by design, not a bug.
>> 
>> Why do you believe that aborting is by design? I would regard it as a bug.
>
> Because the code speaks for itself:
>
>   static Lisp_Object
>   signal_or_quit (Lisp_Object error_symbol, Lisp_Object data, bool keyboard_quit)
>   {
>     [...]
>     if (gc_in_progress || waiting_for_input)  <<<<<<<<<<<<<<<<<<<<<<<<
>       emacs_abort ();
>
> It could be that the reason for that is no longer valid when the
> signal was raised by another thread, via thread-signal.

But I haven't done any user input. I've evaluated the code snippet given
by Gemini, and then I've done nothing. Emacs was idle I believe. And it
aborted.

I will bisect, in order to see where this bug comes from.

Best regards, Michael?




This bug report was last modified 6 years and 313 days ago.

Previous Next


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