🚀 go-pugleaf

My emacs crashes with "Segmentation violation".

System:
*******

 Crash Recurs on:
 ----------------
1. Emacs 18.55/54 on a DEC mips 5000 running Ultrix V3.1D (Rev. 54).
   (tried many times on two different machines to eliminate local factors).
2. Emacs 18.51 on a DEC mips 5000 running Ultrix V4.0 (Rev. 179).

 Can NOT reproduce on:
 ---------------------
3. (Same emacs) on a DEC mips 3100 running Ultrix V2.0 (Rev. 7).
4. Vaxen running BSD.

To Reproduce:
*************
(Notes:
  - needs "hexl-mode" from the archive on tut.cis.ohio-state.edu .
  - all the crashing emacses were compiled in the system (3) above 
    environment (i.e. Ultrix V2.0) )

 A. Start emacs.
 B. Load a big (binary) file (mine was about 800 Kbyte).
 C. Start hexl-mode.
 D. Modify the file.
 E. Save the file.
 F. Kill the buffer. (Not necessary to reproduce the crash).
 G. Do something else (e.g. load and start dired).

  After doing the above, I got the message "Loading dired ..." in the 
minibuffer and a second later emacs crashed with "Segmentation violation" .
  The same happens with other activity in step (G); it may happen after doing
several operations (e.g. when dired is already loaded, it takes several calls
to dired to get to the crash point).
  When following the above steps without using hexl-mode (i.e. change the
binary file directly) emacs does NOT crash. hexl-mode uses some C program
with shell-command-on-region when it starts and when its file is saved.

My guesses:
***********
1. The newer versions of Ultrix have some different way of handling the
   memory. May not recur if emacs were compiled in the new environment (I
   did not try).
2. Some mips 5000 bug (??)

========================================================
*   Boaz Ben-Zvi   (boaz@neutron.lcs.mit.edu)          *
*   MIT: NE43-526   Tel: (617) 253-6212                *
========================================================