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

Previous Next

Full log

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

From: Pip Cet <pipcet <at> protonmail.com>
To: Ihor Radchenko <yantar92 <at> posteo.net>
Cc: 75292 <at> debbugs.gnu.org
Subject: Re: bug#75292: 31.0.50; igc: (file-error "Doing vfork" "Bad address")
Date: Thu, 02 Jan 2025 20:45:40 +0000

"Ihor Radchenko" <yantar92 <at> posteo.net> writes:

> I am getting the belo error regularly, when Emacs is spawning external
> process. Not every time though.

Sounds like something's moved by GC and shouldn't be.  Since you're
running without optimization, it's unlikely that GCC (we don't indicate
the compiler used in report-emacs-bug?  we should) mangled a reference
badly.

The code does assume that SAFE_ALLOCA'd string pointers keep the string
data alive.  That is a bug, and it might cause the behavior you see if,
for some weird reason, we wouldn't be using alloca directly.  But I
think we would be, unless there is something odd about your system.

> See the full backtrace below.
> Please advice what I can do to debug further.

After checking Eli's suggestion, an strace would be nice to find out
which of the pointers has gone bad.

FWIW, I'll try reproducing this now, using your build flags...

Pip

Previous Next

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