GNU bug report logs - #75292
31.0.50; igc: (file-error "Doing vfork" "Bad address")

Previous Next

Package: emacs;

Reported by: Ihor Radchenko <yantar92 <at> posteo.net>

Date: Thu, 2 Jan 2025 17:53:02 UTC

Severity: normal

Found in version 31.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Eli Zaretskii <eliz <at> gnu.org>, Ihor Radchenko <yantar92 <at> posteo.net>
Cc: 75292 <at> debbugs.gnu.org
Subject: bug#75292: 31.0.50; igc: (file-error "Doing vfork" "Bad address")
Date: Thu, 2 Jan 2025 11:41:29 -0800
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....




This bug report was last modified 109 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.