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

Previous Next

Full log

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

From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: oscarfv <at> eclipso.eu, pipcet <at> protonmail.com, 79131 <at> debbugs.gnu.org,
 casouri <at> gmail.com
Subject: Re: bug#79131: 31.0.50; igc: nested signal, SIGSEGV
Date: Fri, 08 Aug 2025 09:10:07 +0200

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

>> From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
>> Cc: pipcet <at> protonmail.com,  oscarfv <at> eclipso.eu,  casouri <at> gmail.com,
>>   79131 <at> debbugs.gnu.org
>> Date: Fri, 08 Aug 2025 08:25:04 +0200
>> 
>> Eli Zaretskii <eliz <at> gnu.org> writes:
>> 
>> >> While an algorithm is working on tree, the tree may temporarily become
>> >> inconsisten. Quitting out of the algorithm where that is the case is a
>> >> no-go.
>> >
>> > Is that related to igc in some way? 
>> 
>> No.
>> 
>> > The discussion was about igc making this happen, or making it happen
>> > more frequently. What you say seem to be unrelated.
>> 
>> More frequently was a hypotheses of Pip, as a side note.
>
> I responded only to that side note.

Then Ipropose to go with whatever Pip finds out to be the best: either
specbind or *_no_quit.

Previous Next

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