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


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

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

> Hello Michael,

Hi Gemini,

>> Tramp propagates all signals to the main thread, otherwise they are not
>> visible. But this might be problematic for the quit signal.
>
> Actually it's problematic for all signals.  I'm traveling this weekend
> and came up with a no-network-required way to reproduce an Emacs
> exit when the main thread is signaled:
>
> Evaluate the following:
>
> (defun my-thread-func ()
>   (sleep-for 5)
>   (thread-signal main-thread 'error "message"))
> (make-thread #'my-thread-func)
>
> Then, within 5 seconds, type C-x C-f.  Wait a few seconds.
> Result: Emacs aborts.

For me, Emacs aborts even w/o any user action. Just waiting.

> 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.

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.