GNU bug report logs - #47067
28.0.50; [feature/native-comp] Crash while scrolling through dispnew.c

Previous Next

Full log

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

From: Andrea Corallo <akrl <at> sdf.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 47067 <at> debbugs.gnu.org
Subject: Re: bug#47067: 28.0.50; [feature/native-comp] Crash while scrolling
 through dispnew.c
Date: Sun, 21 Mar 2021 08:26:45 +0000

Eli Zaretskii <eliz <at> gnu.org> writes:

> A related question: what happens when a .el which was preloaded at
> some point is no longer preloaded?
>
> When it was preloaded, we had its .eln file under native/lisp/, but
> when it ceases to be preloaded, its name is removed from $shortlisp
> (in src/lisp.mk), and we no longer ELC+ELN it during the build.  So we
> now have a stale .eln file in native-lisp, and at some future point in
> time, when that file is loaded into Emacs, it will be
> natively-compiled into ~/.emacs.d/eln-cache/.  At which point we have
> 2 versions of the .eln file.
>
> Question #1: will Emacs load the up-to-date .eln file in eln-cache, or
> could it by any chance load the outdated file in native-lisp?

If the .el file was not changed Emacs will load the original .eln in
'native-lisp' without having to recompile it.

If the .el was modified we will recompile it in 'eln-cache' and load it,
when we do this we clean-up the stale .eln present in
`comp-eln-load-path'.  Unfortunatelly for this case we don't do this for
the last directory in `comp-eln-load-path' (as this is tipically
read-only when Emacs is installed).

> Question #2: can we somehow remove the stale .eln file in these
> situations?

I guess we should make it work for non installed case.

be22cda7be should do this.

Thanks

  Andrea

Previous Next

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