[MacPorts] #33088: xemacs 21.4.22_4 crash

[MacPorts]

#33088: xemacs 21.4.22_4 crash
--------------------------------------+-------------------------------------
 Reporter:  barry.j.mcinnes@…         |       Owner:  macports-tickets@…                   
     Type:  defect                    |      Status:  new                                  
 Priority:  Normal                    |   Milestone:                                       
Component:  ports                     |     Version:  2.0.3                                
 Keywords:  xemacs                    |        Port:  xemacs                               
--------------------------------------+-------------------------------------
 The xemacs builds fine without error, Mac 10.7.2 latest everything

 bash-3.2# port installed xemacs
 The following ports are currently installed:
   xemacs @21.4.22_4 (active)
 bash-3.2#
 Starts up fine, then crashes all the time using the following sequence
 ESC X
 font-lock-mode

 [mac27:~] bmcinnes% xemacs

 Fatal error (11).

 Your files have been auto-saved.
 Use `M-x recover-session' to recover them.

 Your version of XEmacs was distributed with a PROBLEMS file that  may
 describe
 your crash, and with luck a workaround.  Please check it first, but do
 report
 the crash anyway.  Please report this bug by invoking M-x report-emacs-
 bug,
 or by selecting `Send Bug Report' from the Help menu.  If necessary, send
 ordinary email to `xemacs-beta at xemacs.org'.  *MAKE SURE* to include the
 XEmacs
 configuration from M-x describe-installation, or equivalently the file
 Installation in the top of the build tree.

 *Please* try *hard* to obtain a C stack backtrace; without it, we are
 unlikely
 to be able to analyze the problem.  Locate the core file produced as a
 result
 of this crash (often called `core' or `core.<process-id>', and located in
 the directory in which you started XEmacs or your home directory), and
 type

   gdb /opt/local/bin/xemacs core

 then type `where' at the debugger prompt.  No GDB on your system?  You may
 have DBX, or XDB, or SDB.  (Ask your system administrator if you need
 help.)
 If no core file was produced, enable them (often with `ulimit -c
 unlimited'
 in case of future recurrance of the crash.

 Lisp backtrace follows:

   dispatch-non-command-events()
   # (condition-case ... . ((nil)))
   progress-feedback-dispatch-non-command-events()
   # bind (tmsg top frame value message label)
   append-progress-feedback(font-lock "Fontifying *scratch*..." 0 nil)
   # bind (frame value message label)
   display-progress-feedback(font-lock "Fontifying *scratch*..." 0)
   # bind (str)
   # (unwind-protect ...)
   # bind (args value fmt label)
   progress-feedback-with-label(font-lock "Fontifying %s..." 0 "*scratch*")
   # bind (maybe-loudly end beg)
   font-lock-default-unfontify-region(1 198 t)
   # bind (loudly end beg)
   font-lock-unfontify-region(1 198 t)
   # bind (was-on font-lock-verbose font-lock-message-threshold aborted)
   # (unwind-protect ...)
   font-lock-default-fontify-buffer()
   # bind (font-lock-verbose)
   font-lock-fontify-buffer()
   # bind (on-p maximum-size arg)
   font-lock-mode(nil)
   # bind (command-debug-status)
   call-interactively(font-lock-mode)
   command-execute(font-lock-mode t)
   # bind (_execute_command_keys_ _execute_command_name_ prefix-arg)
   execute-extended-command(nil)
   # bind (command-debug-status)
   call-interactively(execute-extended-command)
   # (condition-case ... . error)
   # (catch top-level ...)
 Segmentation fault

-- 
Ticket URL: <https://trac.macports.org/ticket/33088>
MacPorts <http://www.macports.org/>
Ports system for Mac OS