GNU bug report logs -
#76546
30.1; Native compilation is corrupting lambdas/closures stored in variables after some time
Previous Next
Full log
Message #29 received at 76546 <at> debbugs.gnu.org (full text, mbox):
Yes maybe, it was apparent from the error message that the function had unexpected data and trying to print it crashed Emacs.. I will check for an old log
But this error has been present for many years so it is not a new thing, I solved it by not byte compilling some files
> Eli Zaretskii <eliz <at> gnu.org> kirjoitti 2025-04-26 kello 13.45:
>
>
>>
>> Cc: 76546 <at> debbugs.gnu.org, acorallo <at> gnu.org
>> Date: Tue, 15 Apr 2025 11:38:34 +0300
>> From: Eli Zaretskii <eliz <at> gnu.org>
>>
>>> From: Christian Johansson <christian <at> cvj.se>
>>> Date: Tue, 15 Apr 2025 09:58:07 +0200
>>> Cc: Eli Zaretskii <eliz <at> gnu.org>, 76546 <at> debbugs.gnu.org
>>>
>>> I have one issue that is reproducible but only after a couple of days of Emacs running and exahausting the memory, in that case the lambda stored in variable becomes binary and printing it crashes Emacs
>>
>> If the value cannot be printed, how do you know that it is binary?
>>
>> Could you perhaps run Emacs under GDB, so that when this happens, you
>> could show the value and perhaps invoke some other commands we would
>> like you to try and show the results?
>
> Ping! Any further information or progress with this?
This bug report was last modified 26 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.