From: Michael Albinus <michael.albinus@gmx.de>
To: Dima Kogan <dima@secretsauce.net>
Cc: 49954@debbugs.gnu.org
Subject: bug#49954: 28.0.50; TRAMP: cannot kill child processes: "Forbidden reentrant call of Tramp"
Date: Thu, 16 Sep 2021 17:42:23 +0200 [thread overview]
Message-ID: <87v930msrk.fsf@gmx.de> (raw)
In-Reply-To: <87o88uisee.fsf@secretsauce.net> (Dima Kogan's message of "Tue, 14 Sep 2021 17:39:21 -0700")
Dima Kogan <dima@secretsauce.net> writes:
Hi Dima,
> Thanks for the explanation. What would be an example of an asynchronous
> process? I have several remote 'M-x shell' buffers and probably some
> dired buffers looking at remote directories. Is each 'M-x shell' child
> an "asynchronous process" for the purposes of this issue?
It is an synchronous process, indeed.
> Does it make sense to you that disabling caching fixes it?
>
> Usually, I can C-c in "M-x shell" just fine. When this bug is triggered,
> though, I cannot C-c in remote M-x shell processes at all: it fails each
> time. Disabling the caching, getting one successful C-c, and re-enabling
> it makes it work that time and in the future. Is this consistent with
> the failure mechanism you're thinking of?
Why do you mess with Tramp's cache? Adding remote-file-error to
debug-ignored-errors, as I have recommended, shall mask the error
sufficiently.
> Thanks
Best regards, Michael.
next prev parent reply other threads:[~2021-09-16 15:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 9:08 bug#49954: 28.0.50; TRAMP: cannot kill child processes: "Forbidden reentrant call of Tramp" Dima Kogan
2021-08-09 12:33 ` Michael Albinus
2021-08-10 4:26 ` Dima Kogan
2021-08-10 13:52 ` Michael Albinus
2021-09-11 8:32 ` Dima Kogan
2021-09-11 12:19 ` Michael Albinus
2021-09-15 0:39 ` Dima Kogan
2021-09-15 19:25 ` Dima Kogan
2021-09-16 15:45 ` Michael Albinus
2021-09-16 15:42 ` Michael Albinus [this message]
2021-09-16 17:17 ` Dima Kogan
2021-09-16 17:36 ` Michael Albinus
2021-09-18 20:18 ` Dima Kogan
2021-09-18 20:50 ` Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v930msrk.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=49954@debbugs.gnu.org \
--cc=dima@secretsauce.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).