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: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Albinus <michael.albinus <at> gmx.de>
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: Sat, 25 Aug 2018 15:42:45 +0300
> From: Michael Albinus <michael.albinus <at> gmx.de>
> Cc: gazally <at> runbox.com,  32502 <at> debbugs.gnu.org
> Date: Sat, 25 Aug 2018 12:53:02 +0200
> 
> > Michael, unless I'm missing something, it sounds like Tramp signals
> > the main thread in this scenario.  (current_thread->error_symbol is
> > only set by thread-signal.)  Is that really necessary?  If so, can you
> > describe why you needed to signal the main thread, while it was
> > waiting for input?
> 
> Tramp propagates all signals to the main thread, otherwise they are not
> visible.

Is that wise?  It means that if a user is doing something in the main
thread while the Tramp threads run asynchronously, the user's program
will/might error out.

> However, if we apply this I don't know how to quit (let's say) 250
> threads. One quit signal is good for one thread only. I believe we need
> also a mechanism to quit many threads at once.

I think we should simply make thread-signal a no-op when it signals
the main thread during the time the main thread is waiting for input.




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.