GNU bug report logs -
#75632
31.0.50; igc: Crash report
Previous Next
Reported by: Ihor Radchenko <yantar92 <at> posteo.net>
Date: Fri, 17 Jan 2025 14:35:02 UTC
Severity: normal
Found in version 31.0.50
Done: Pip Cet <pipcet <at> protonmail.com>
Bug is archived. No further changes may be made.
Full log
Message #16 received at 75632-done <at> debbugs.gnu.org (full text, mbox):
"Ihor Radchenko" <yantar92 <at> posteo.net> writes:
> Pip Cet <pipcet <at> protonmail.com> writes:
>
>> "Ihor Radchenko" <yantar92 <at> posteo.net> writes:
>>
>>> Just got the following:
>>
>> Yes, that's the signal handling bug. I'm not entirely sure why we
>> removed the fix that was in scratch/igc, but we did, so we need another
>> one.
>> ...
>> to handle_user_signal, which will silently ignore SIGUSR* received while
>> MPS may have locked the arena.
>
> I indeed sent SIGUSR2 just before I saw the crash.
It'd be nice if that simply worked. I think debugging with SIGUSR* is
important, so I've pushed a fix (and I'm closing this bug; if further
discussion is needed, feel free to revert and reopen).
> For some context (maybe irrelevant), Emacs hung while performing magit
> commit (C-c C-c in magit commit buffer; and the commit was actually
> written before the hang). It only ever happened for me on igc branch.
Thanks! Too bad we lost that backtrace, then. If it happens again,
please let us know!
(I'm using magit, and I know it waits for subprocesses, so I'll go over
the SIGCHLD handling code to ensure we never drop one of them).
Pip
This bug report was last modified 115 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.