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

Message #23 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 22:22:09 +0200

> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: eggert <at> cs.ucla.edu, 75292 <at> debbugs.gnu.org
> Date: Thu, 02 Jan 2025 19:37:00 +0000
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > 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?
> 
> Should I pass some ./configure option? Or do you want me to modify the
> sources directly?

I think you just need to recompile callproc.c and then relink.  Like
this:

  $ cd src
  $ make callproc.o -W callproc.c MYCPPFLAGS='-DUSABLE_POSIX_SPAWN=0'
  $ cd .. && make
This bug report was last modified 110 days ago.

Previous Next

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