all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tomas Hlavaty <tom@logand.com>
To: Hongyi Zhao <hongyi.zhao@gmail.com>,
	Emanuel Berg <moasenwood@zoho.eu>,
	help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: /usr/local/bin/emacs: writing to child signal FD: Bad file descriptor
Date: Sat, 04 Dec 2021 13:05:44 +0100	[thread overview]
Message-ID: <87r1aslgmf.fsf@logand.com> (raw)
In-Reply-To: <CAGP6POLC+reyGrPvY9WSGQZuCpedyOupYcHf-NdY8zdd2yF6+A@mail.gmail.com>

On Sat 04 Dec 2021 at 11:26, Hongyi Zhao <hongyi.zhao@gmail.com> wrote:
> I try to compile vterm module with `M-x vterm-module-compile RET`, but
> Emacs freezes. Then I killed the process by hitting `C-g` twice, at
> this moment the message reported here occured.

There is something seriously wrong with C-g.
It is very dangerous.

Emacs often crashes for me after trying to break blocking operation
using C-g twice.
It just prints a list of threads and crashes.
This has been happening for a long time;
I guess since introduction of threads.
It probably has something to do with disruption of blocking
network operations or garbage collection.

Two weeks ago, it even truncated ~/.emacs to 0 size.  This happened once
so far.

All with emacs -nw.

Tomas



  parent reply	other threads:[~2021-12-04 12:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-04  1:12 /usr/local/bin/emacs: writing to child signal FD: Bad file descriptor Hongyi Zhao
2021-12-04  2:32 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-04  3:26   ` Hongyi Zhao
2021-12-04  3:32     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-12-04 12:05     ` Tomas Hlavaty [this message]
2021-12-04 12:16       ` Po Lu
2021-12-04 13:28       ` Eli Zaretskii
2021-12-04 20:37         ` Tomas Hlavaty
2021-12-04 20:44           ` Eli Zaretskii
2021-12-04 21:32             ` Tomas Hlavaty

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r1aslgmf.fsf@logand.com \
    --to=tom@logand.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=hongyi.zhao@gmail.com \
    --cc=moasenwood@zoho.eu \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.