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


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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Helmut Eller <eller.helmut <at> gmail.com>
Cc: gerd.moellmann <at> gmail.com, spd <at> toadstyle.org, pipcet <at> protonmail.com,
 79116 <at> debbugs.gnu.org
Subject: Re: bug#79116: 31.0.50; Crash on IGC build
Date: Fri, 01 Aug 2025 08:59:12 +0300
> From: Helmut Eller <eller.helmut <at> gmail.com>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  spd <at> toadstyle.org,
>   pipcet <at> protonmail.com,  79116 <at> debbugs.gnu.org
> Date: Thu, 31 Jul 2025 18:46:49 +0200
> 
> Anyway, my concern is a bit more general: I think that objects without
> memory barriers, (e.g. structs allocated with malloc) should be scanned
> as roots.

This is very general, and in that general form quite scary.  Emacs
allocates with malloc all over the place, and most such allocations
have nothing to do with Lisp objects.  So I hope we can have rules
that determine whether a given malloc'ed object needs to be scanned or
not, because otherwise we'll force MPS to scan too much, and lose the
single most important advantage it gives us: that its GC cycles are
fast and don't stop the application code for prolonged periods of
time.




This bug report was last modified 17 days ago.

Previous Next


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