GNU bug report logs - #79131
31.0.50; igc: nested signal, SIGSEGV

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Gerd Möllmann <gerd.moellmann <at> gmail.com>
Cc: oscarfv <at> eclipso.eu, pipcet <at> protonmail.com, 79131 <at> debbugs.gnu.org, casouri <at> gmail.com
Subject: bug#79131: 31.0.50; igc: nested signal, SIGSEGV
Date: Sun, 03 Aug 2025 22:00:56 +0300

> From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
> Cc: Pip Cet <pipcet <at> protonmail.com>,  oscarfv <at> eclipso.eu,
>   casouri <at> gmail.com,  79131 <at> debbugs.gnu.org
> Date: Sun, 03 Aug 2025 18:17:17 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> Date: Sun, 03 Aug 2025 15:47:43 +0000
> >> From: Pip Cet <pipcet <at> protonmail.com>
> >> Cc: Óscar Fuentes <oscarfv <at> eclipso.eu>, Eli Zaretskii <eliz <at> gnu.org>, Yuan Fu <casouri <at> gmail.com>, 79131 <at> debbugs.gnu.org
> >> 
> >> Gerd Möllmann <gerd.moellmann <at> gmail.com> writes:
> >> 
> >> > Pip Cet <pipcet <at> protonmail.com> writes:
> >> >
> >> >> But I'll wait for others to weigh in; maybe my theory is obviously
> >> >> incorrect.
> >> >
> >> > I think the memq thing is definitely a bug.
> >> 
> >> Unfortunately, while Fmemq and Fassq are easy to fix, Fget can also quit
> >> (if overriding-plist-environment is in use), and that's used in a few
> >> places here.  Do we need get_no_quit?
> >
> > Maybe we should inhibit_igc instead (if we don't already)?  Otherwise,
> 
> You mean inhibit-quit?

No, I mean prevent MPS from interrupting a given short sequence of
code with GC.

Previous Next

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