unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Thomas Düssel via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>
Cc: 70517@debbugs.gnu.org
Subject: bug#70517: 29.3; suspicious error message from compile command in Emacs 29.3
Date: Tue, 23 Apr 2024 00:30:41 +0200	[thread overview]
Message-ID: <e8046d31-e0dc-44f3-bb30-0fda10bb11aa@gmx.de> (raw)
In-Reply-To: <867cgp5gpy.fsf@gnu.org>


On 4/22/24 21:40, Eli Zaretskii wrote:
>> Date: Mon, 22 Apr 2024 17:55:24 +0200
>> From:  Thomas Düssel via "Bug reports for GNU Emacs,
>>   the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> The following error message appears in the terminal from which emacs was
>> started every time I use the 'compile' command:
>>
>>   > emacs: writing to child signal FD: Invalid argument
>>
>> The compilation itself (via make) works perfectly fine. Only this new
>> message is a bit annoying. And so cryptic, isn't it? It did not appear
>> up until the latest update.
>>
>> This error message (or whatever it is) appears also, when I start emacs
>> from a non-X tty (Ctrl + Alt + F2) and with '-Q' option. To be precise,
>> it appears when I use 'M-x compile' and for longer compilation processes
>> it appears at the end of the compilation, not at the beginning.
> When a sub-process exits, Emacs writes to file descriptor which it
> monitors with pselect.  This is so we don't miss SIGCHLD for some
> reason.  Why in your case this write errors out with EINVAL, I don't
> know.  Perhaps Paul (CC'ed) could have some ideas.
>
> If this could happen for benign reasons, maybe we should silently
> ignore these errors.

Thanks for that clarification... I received my version of 29.3 as a
regular package update
for slackware 15. My system is pimped with some 32bit libraries from
alienbob,
another distributer of slackware packages. As a user with little to no
insight in the emacs
internals I would like to know, if this error message appears on other
systems aswell and
on other slackware systems in particular. Maybe the bug-report has to go
to the slackware
package maintainer?







  parent reply	other threads:[~2024-04-22 22:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 15:55 bug#70517: 29.3; suspicious error message from compile command in Emacs 29.3 Thomas Düssel via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-22 19:40 ` Eli Zaretskii
2024-04-22 19:50   ` Paul Eggert
2024-04-23  5:04     ` Eli Zaretskii
2024-04-22 22:30   ` Thomas Düssel via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-04-23  5:54     ` Eli Zaretskii
     [not found]       ` <8d6e333d-b2a0-46ef-96ba-d0a58b668e76@gmx.de>
2024-04-24 15:30         ` Eli Zaretskii

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=e8046d31-e0dc-44f3-bb30-0fda10bb11aa@gmx.de \
    --to=bug-gnu-emacs@gnu.org \
    --cc=70517@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=th.duessel@gmx.de \
    /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).