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

Previous Next

Package: emacs;

Reported by: Eli Zaretskii <eliz <at> gnu.org>

Date: Thu, 11 Mar 2021 11:28:02 UTC

Severity: normal

Found in version 28.0.50

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

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Andrea Corallo <akrl <at> sdf.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 47067 <at> debbugs.gnu.org
Subject: bug#47067: 28.0.50; [feature/native-comp] Crash while scrolling through dispnew.c
Date: Thu, 25 Mar 2021 16:51:48 +0000
Andrea Corallo <akrl <at> sdf.org> writes:

> Eli Zaretskii <eliz <at> gnu.org> writes:
>
>>> From: Andrea Corallo <akrl <at> sdf.org>
>>> Cc: 47067 <at> debbugs.gnu.org
>>> Date: Sun, 21 Mar 2021 16:41:14 +0000
>>> 
>>> I was referring to a different case, future dumps done by the user
>>> calling directly `dump-emacs-portable', in that case some .eln might
>>> stay where they were placed originally (not in the preloaded subfolder).
>>> 
>>> I know for now we don't support officially `dump-emacs-portable' to be
>>> used directly by the user, so I'm not sure that's a real issue, but I
>>> was trying to think future proof.
>>
>> Ah, okay.  I think we can leave this use case for posterity, to be
>> figured out when re-dumping is fully supported.  How about adding this
>> bit to the etc/TODO item that talks about re-dumping?
>
> Right, will do that contextually when I prepare the patch.
>
>   Andrea

The only non trivial part here is to identify at compile time if a file
will be preloaded or not (so we can output it in the preloaded
directory).

Any obvious suggestion here before I start hacking the build system?

TIA

  Andrea




This bug report was last modified 4 years and 44 days ago.

Previous Next


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