Re: igc, macOS avoiding signals

[Gerd Möllmann]

Pip Cet <pipcet@protonmail.com> writes:

>> With
>>
>>   modified   src/profiler.c
>>   @@ -347,7 +347,7 @@ record_backtrace (struct profiler_log *plog, EMACS_INT 
>> count)
>>    add_sample (struct profiler_log *plog, EMACS_INT count)
>>    {
>>    #ifdef HAVE_MPS
>>   -  if (igc_busy_p ())
>>   +  if (false)
>>    #else
>>      if (EQ (backtrace_top_function (), QAutomatic_GC)) /* bug#60237 */
>>    #endif
>
> This is after removing gc_signal_handler_can_run, right?

Right. And meanwhile it also survived the same parsing 100 times in a
loop with profiling on around it. 

> Even if, in addition, I block signals in the SIGSEGV handler, I see
> crashes here, FWIW, but not quite every time that recipe is run.  It
> seems to work even less reliably when rr is in use (and then I realized
> I was running an optimized build so the trace was useless, sigh).
>
> I'd still like to see at least one crash on macOS, but there's nothing
> I'm aware of that would prevent such crashes, only make them (maybe
> much) less likely.  For starters, fewer pages so fewer barriers :-)
>
> Pip

Me too, but I agree with you. It should eventually freeze, there's
nothing preventing it that I could point to.