GNU bug report logs - #79116
31.0.50; Crash on IGC build

Previous Next

Package: emacs;

Reported by: Sean Devlin <spd <at> toadstyle.org>

Date: Mon, 28 Jul 2025 18:32:01 UTC

Severity: normal

Found in version 31.0.50

Full log


View this message in rfc822 format

From: Pip Cet <pipcet <at> protonmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: spd <at> toadstyle.org, 79116 <at> debbugs.gnu.org
Subject: bug#79116: 31.0.50; Crash on IGC build
Date: Wed, 30 Jul 2025 12:57:55 +0000
"Eli Zaretskii" <eliz <at> gnu.org> writes:

>> Date: Wed, 30 Jul 2025 12:30:31 +0000
>> From: Pip Cet <pipcet <at> protonmail.com>
>> Cc: spd <at> toadstyle.org, 79116 <at> debbugs.gnu.org
>>
>> "Eli Zaretskii" <eliz <at> gnu.org> writes:
>>
>> >> Cc: 79116 <at> debbugs.gnu.org
>> >> Date: Tue, 29 Jul 2025 18:18:05 +0000
>> >> From:  Pip Cet via "Bug reports for GNU Emacs,
>> >>  the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
>> >>
>> >> "Sean Devlin" <spd <at> toadstyle.org> writes:
>> >>
>> >> > Hi folks,
>> >> >
>> >> > I left Emacs idle overnight, and I found a crash log when I returned in
>> >> > the morning. Please see the attached file.
>> >> >
>> >> > I'm using the IGC branch, and it looks like a related assertion failed.
>> >> >
>> >> > I have igc-step-interval set to 0.05, but no other configuration related to GC.
>> >> >
>> >> > I don’t know how to reproduce the error.
>> >> >
>> >> > Thanks!
>> >>
>> >> Thanks for the report. I'm afraid we don't have very much to go on: this
>> >> assertion in trace.c in MPS failed:
>> >>
>> >>     AVER(RefSetSub(ScanStateUnfixedSummary(ss), SegSummary(seg))); /* <design/check/#.common> */
>> >>
>> >> I think that means a memory structure internal to MPS must have been
>> >> corrupted; either the ScanState on the stack, or the segment
>> >> information.
>> >
>> > Do you understand how come a non-main thread called MPS in this case?
>>
>> Yes, MPS uses a separate thread to handle Mach exceptions on macOS,
>> rather than a signal handler.
>
> Are we sure this is that separate thread?

Yes, we are.

> What are the indications of that?

The backtrace clearly indicates that thread 1 is the one running code
from protxc.c, and it is thread 1 which crashed.

Pip





This bug report was last modified 18 days ago.

Previous Next


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