Emacs 29.3; suspicious error message from compile command in Emacs 29.3
by 3Tom from LinuxQuestions.org on (#6M973)
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.
I asked for help with that at the GNU bugtracker and got the following answer:
> On 4/22/24 21:40, Eli Zaretskii wrote:
>> 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.
And then:
> 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.
I asked for help with that at the GNU bugtracker and got the following answer:
> On 4/22/24 21:40, Eli Zaretskii wrote:
>> 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.
And then:
Please do report to them (slackware), it cannot possibly do any harm. When youMy question here: Gets anyone the same message when using the M-x compile command in Emacs 29.3 on slackware? And if so, where is the correct place for filing a bug report?
do, please ask them to tell us here whether this could be caused by
some downstream change they made in Emacs, or by some of the libraries
you have installed.