From 0aa4958b483fca10faabb4c1e6fcbc732a97a5e9 Mon Sep 17 00:00:00 2001 From: Pip Cet Date: Wed, 21 Aug 2024 08:59:25 +0000 Subject: [PATCH] Pure storage removal: Documentation * etc/NEWS: Document removal of unexec dumper. * etc/PROBLEMS: Remove pure space problems. (cherry picked from commit 1c495735b4fd7411bca39161b45e0115d0d377b9) --- etc/PROBLEMS | 32 -------------------------------- 1 file changed, 32 deletions(-) diff --git a/etc/PROBLEMS b/etc/PROBLEMS index 4496b9c7968..c9a208518d2 100644 --- a/etc/PROBLEMS +++ b/etc/PROBLEMS @@ -4161,31 +4161,6 @@ prints a nonzero value. You can temporarily disable it as follows: As with randomize_va_space, you can re-enable Exec-shield when you are done, by echoing the original value back to the file. -*** temacs prints "Pure Lisp storage exhausted". - -This means that the Lisp code loaded from the .elc and .el files during -'temacs --batch --load loadup dump' took up more space than was allocated. - -This could be caused by - 1) adding code to the preloaded Lisp files - 2) adding more preloaded files in loadup.el - 3) having a site-init.el or site-load.el which loads files. - Note that ANY site-init.el or site-load.el is nonstandard; - if you have received Emacs from some other site and it contains a - site-init.el or site-load.el file, consider deleting that file. - 4) getting the wrong .el or .elc files - (not from the directory you expected). - 5) deleting some .elc files that are supposed to exist. - This would cause the source files (.el files) to be - loaded instead. They take up more room, so you lose. - 6) a bug in the Emacs distribution which underestimates the space required. - -If the need for more space is legitimate, change the definition -of PURESIZE in puresize.h. - -But in some of the cases listed above, this problem is a consequence -of something else that is wrong. Be sure to check and fix the real problem. - *** openSUSE 10.3: Segfault in bcopy during dumping. This is due to a bug in the bcopy implementation in openSUSE 10.3. @@ -4205,13 +4180,6 @@ binary null characters, and the 'file' utility says: We don't know what exactly causes this failure. A work-around is to build Emacs in a directory on a local disk. -*** The dumped Emacs crashes when run, trying to write pure data. - -On a system where getpagesize is not a system call, it is defined -as a macro. If the definition (in both unex*.c and malloc.c) is wrong, -it can cause problems like this. You might be able to find the correct -value in the man page for a.out(5). - * Problems on legacy systems This section covers bugs reported on very old hardware or software. -- 2.39.5