rbbb%rice@sri-unix.UUCP (01/10/84)
From: David Chase <rbbb@rice> I spent several days tearing into emacs (version 264) trying to find the cause of mysterious "bus errors" and "segmentation violations". Much by chance, I discovered that I was overflowing the "macro" table. Now, there is code in macro.c that looks like it would prevent such a thing from ever happening, but clearly it did not. This bug appears to be tickled by (obviously) using all of the macro table via defun's, autoloads, macros, &c. Trying to autoload and run a subshell in a window then causes the dump. Has anyone out there had similar problems? Has anyone received anything from UniPress in the way of bug fixes or advice?
Robert.Thornton@CMU-CS-CAD.ARPA (01/13/84)
I have had similar problems with version 264 on Suns which were due to too many mlisp functions. My quick fix was to increase the value of maxmacs in macros.h (it seems that its value is twice the number of functions which may be defined and comes as 600 -- 300 functions.) There are several other bugs which dereference 0 as an address which show up as an ungracefull exit on the Sun but never show up on the vax cause it doesn't mind if you look at 0. -Robert