From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 75292@debbugs.gnu.org, yantar92@posteo.net
Subject: bug#75292: 31.0.50; igc: (file-error "Doing vfork" "Bad address")
Date: Thu, 02 Jan 2025 22:35:06 +0200 [thread overview]
Message-ID: <86ikqxhs3p.fsf@gnu.org> (raw)
In-Reply-To: <6f1070fd-b2c8-47c6-a8b8-26325d620cb4@cs.ucla.edu> (message from Paul Eggert on Thu, 2 Jan 2025 11:41:29 -0800)
> Date: Thu, 2 Jan 2025 11:41:29 -0800
> Cc: 75292@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
>
> On 2025-01-02 11:29, Eli Zaretskii wrote:
> >>>> Debugger entered--Lisp error: (file-error "Doing vfork" "Bad address")
> >>>> (call-process-shell-command "grep -anE '^:(Sourc.URL\\+?):[ \11[]+https://curiouscoding\\.nl/posts/static-search-tree/[]]*$' '/home/yantar92/Org/rss_archive_2019.org'" nil t)
> ...
> > Could it be that this started happening when we began using
> > posix_spawn instead of vfork?
>
> If Emacs uses posix_spawn instead of vfork, shouldn't file-error report
> "Doing posix_spawn" instead of "Doing vfork"? Truth in advertising and
> all that....
We should, but it looks like someone didn't want to condition the
value of CHILD_SETUP_ERROR_DESC by USABLE_POSIX_SPAWN...
next prev parent reply other threads:[~2025-01-02 20:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 17:54 bug#75292: 31.0.50; igc: (file-error "Doing vfork" "Bad address") Ihor Radchenko
2025-01-02 18:37 ` Eli Zaretskii
2025-01-02 18:42 ` Ihor Radchenko
2025-01-02 19:29 ` Eli Zaretskii
2025-01-02 19:37 ` Ihor Radchenko
2025-01-02 20:22 ` Eli Zaretskii
2025-01-02 20:45 ` Ihor Radchenko
2025-01-02 21:07 ` Eli Zaretskii
2025-01-03 17:56 ` Ihor Radchenko
2025-01-03 19:33 ` Eli Zaretskii
2025-01-04 14:12 ` Ihor Radchenko
2025-01-04 14:20 ` Eli Zaretskii
2025-01-07 17:40 ` Ihor Radchenko
2025-01-07 17:50 ` Eli Zaretskii
2025-01-03 20:21 ` Eli Zaretskii
2025-01-04 14:13 ` Ihor Radchenko
2025-01-04 14:22 ` Eli Zaretskii
2025-01-04 15:21 ` Ihor Radchenko
2025-01-02 19:41 ` Paul Eggert
2025-01-02 20:35 ` Eli Zaretskii [this message]
2025-01-02 20:45 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-03 17:58 ` Ihor Radchenko
2025-01-03 18:24 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-03 19:47 ` Eli Zaretskii
2025-01-03 19:51 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-03 19:11 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86ikqxhs3p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=75292@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=yantar92@posteo.net \
/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).