Re: igc, macOS avoiding signals

[Pip Cet]

Pip Cet <pipcet@protonmail.com> writes:

> "Helmut Eller" <eller.helmut@gmail.com> writes:
>>> I find that difficult to understand. But it may be just a
>>> statistical phenomenon. Maybe filling up an APs memory is so fast so
>>> that the probability of a signal hitting while owning the mutex is close
>>> to zero, or something.
>>
>> Very few of Emacs' signal handlers actually touch a barrier.  I've also
>
> Indeed.  These crashes are rare in typical usage, which doesn't mean we
> should delay fixing them until Emacs is "unstable enough".  It already
> is, IMHO, because we take that approach too frequently.
>
>> not seen any reproducable receipes for the "signal issues" that the igc
>> branch supposedly has.
>
> Removing the SIGPROF protection code should allow Ihor's recipe to crash
> again.

Confirmed.  Here's the recipe (which, yes, you have already seen):

https://lists.gnu.org/archive/html/emacs-devel/2024-06/msg00560.html

Make igc_busy_p () return false (as we could do if the "supposed" signal
issue weren't real), immediate crash.

Pip