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

Previous Next

Full log

Message #14 received at 75292 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ihor Radchenko <yantar92 <at> posteo.net>
Cc: 75292 <at> debbugs.gnu.org, eggert <at> cs.ucla.edu
Subject: Re: bug#75292: 31.0.50; igc: (file-error "Doing vfork" "Bad address")
Date: Thu, 02 Jan 2025 21:29:45 +0200

> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: Paul Eggert <eggert <at> cs.ucla.edu>, 75292 <at> debbugs.gnu.org
> Date: Thu, 02 Jan 2025 18:42:14 +0000
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> 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)
> >
> > Is this something new?  If so, did you update some system libraries
> > lately?
> 
> I am seeing it since long time ago.

Could it be that this started happening when we began using
posix_spawn instead of vfork?  If you rebuild Emacs disabling
USABLE_POSIX_SPAWN, does the problem go away?

Previous Next

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