GNU bug report logs - #75209
30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld"

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ihor Radchenko <yantar92 <at> posteo.net>
Cc: 75209 <at> debbugs.gnu.org, njackson <at> posteo.net
Subject: bug#75209: 30.0.93; Emacs reader failed to read data in "/home/nlj/.cache/org-persist/gc-lock.eld"
Date: Sat, 15 Mar 2025 14:45:44 +0200

> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: Eli Zaretskii <eliz <at> gnu.org>, 75209 <at> debbugs.gnu.org
> Date: Sat, 15 Mar 2025 12:19:07 +0000
> 
> Ihor Radchenko <yantar92 <at> posteo.net> writes:
> 
> > Never returned likely means that it threw an error.
> > Most likely because
> >
> > (setf (alist-get before-init-time alist nil nil #'equal)
> >             (current-time))
> > will fail when ALIST is nil. I should fix this.
> 
> I was wrong. if ALIST is nil, the above code should work just fine.
> So, it looks like all the problems boil down to incomplete read.

Could the code which writes the file do it in atomic fashion,
i.e. write a temporary file, then rename the original file, then move
the new to the original's name, then delete the original file?

(On Posix filesystems moving a file to the original name is an atomic
operation, but not on MS-Windows, which is why I suggest a slightly
more complicated procedure.)

Previous Next

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