From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@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 03:32:52 +0100 [thread overview]
Message-ID: <87k0glw14b.fsf@zoho.eu> (raw)
In-Reply-To: CAGP6PO+mH2DucYYi=FnrojDfYJdJEWO3T9Aifx-v9KA0_C7fgw@mail.gmail.com
Hongyi Zhao wrote:
> werner@X10DAi-00:~$ emacs
> /usr/local/bin/emacs: writing to child signal FD: Bad file descriptor
That's often buffer overflow ... ha, old school!
What did you do?
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-12-04 2:32 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 [this message]
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
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=87k0glw14b.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--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.
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).