unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: /usr/local/bin/emacs: writing to child signal FD: Bad file descriptor
Date: Sat, 04 Dec 2021 15:28:40 +0200	[thread overview]
Message-ID: <4AAA998C-9EBE-48F2-9758-DF7D64B4E78F@gnu.org> (raw)
In-Reply-To: <87r1aslgmf.fsf@logand.com>

On December 4, 2021 2:05:44 PM GMT+02:00, Tomas Hlavaty <tom@logand.com> wrote:
> 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.

What version of Emacs is that, and on what OS?

In general, typing C-g twice invokes "emergency exit", but that is supposed to ask you a question before it ends the session.




  parent reply	other threads:[~2021-12-04 13:28 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
2021-12-04 12:16       ` Po Lu
2021-12-04 13:28       ` Eli Zaretskii [this message]
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

  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=4AAA998C-9EBE-48F2-9758-DF7D64B4E78F@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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).