xemacs 21.4.22_4 crash when entering font-lock-mode

[basmac]

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@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

[basmac]

Works fine under 10.6.8

[mark@…]

Confirmed, similar set up as Barry. I went back a few versions too, but couldn't find one that worked on Lion 10.7.3 :-(

[basmac]

Replying to mark@…:

Confirmed, similar set up as Barry. I went back a few versions too, but couldn't find one that worked on Lion 10.7.3 :-(

Sent information and coredump to xemacs-beta as requested above.

[basmac]

The recommended fix is from xemacs-beta

To avoid the segfault,

M-x customize-variable RET progress-feedback-use-echo-area RET

and set it to t.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #33614.

Please remember to use WikiFormatting when writing in Trac.

[matteocorti (Matteo Corti)]

Cc Me!

[matteocorti (Matteo Corti)]

Confirmed on 10.8.1.

I had no problems until I re-installed all the ports. This might mean that a dependency is missing since it was working on the same system with many more ports installed ...

[andre.holzner@…]

in order not to have to type the fix suggested by Barry each time I start xemacs, I have put the following line into my xemacs startup file (should be the equivalent 'non-interactive' command):

(setq progress-feedback-use-echo-area t)

[petrrr]

I experience crashes of xemacs which might be related, at least to me very similar. I realized it occurs when I activate "syntax highlighting", which was activated automatically first.

My OS version is Mac OS X 10.5.8 (9L31a Xcode 3.1.4 Component versions: DevToolsCore-1204.0; DevToolsSupport-1186.0 BuildVersion: 9M2809 MacPorts base version 2.1.2 installed

For me the problem appeared only with the update to xemacs @21.4.22_5, so I switched back to xemacs @21.4.22_4, which for me works fine. However, now xemacs @21.4.22_6 links against libpng @1.5.12_0 and it becomes less practical to stay with the older version. As this problem appeared only with a port revision I would assume it is NOT a problem of the xemacs release itself.

[urquell:~] petr% xemacs .cshrc

Fatal error (10).

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

... and the lisp traceback

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 .cshrc..." 0 nil)
  # bind (frame value message label)
  display-progress-feedback(font-lock "Fontifying .cshrc..." 0)
  # bind (str)
  # (unwind-protect ...)
  # bind (args value fmt label)
  progress-feedback-with-label(font-lock "Fontifying %s..." 0 ".cshrc")
  # bind (maybe-loudly end beg)
  font-lock-default-unfontify-region(1 3070 t)
  # bind (loudly end beg)
  font-lock-unfontify-region(1 3070 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()
  (progn (font-lock-mode) (customize-set-variable (quote font-lock-mode) font-lock-mode))
  eval((progn (font-lock-mode) (customize-set-variable (quote font-lock-mode) font-lock-mode)))
  # (condition-case ... . error)
  # (catch top-level ...)
Bus error

[petrrr]

Cc Me!

[jay.larson@…]

Sadly, this problem persists on OS X 10.9.2 and MacPorts 2.2.1. Is anybody trying to fix this? I'm not really up to the job nor so-inclined, but find this situation very annoying.

[jim@…]

Replying to jay.larson@…:

Sadly, this problem persists on OS X 10.9.2 and MacPorts 2.2.1. Is anybody trying to fix this? I'm not really up to the job nor so-inclined, but find this situation very annoying.

I firmly believe that this is a MacPorts problem as the issue does not exist with this or any other version of xemacs on other operating systems (Linux, FreeBSD, or Solaris) as far as I've seen.

The (setq progress-feedback-use-echo-area t) does work, but I don't see why it should be necessary.

[lpagani91]

This problem never occured on XEmacs installed on OS X 10.7.5 (and previous versions) when XEmacs was installed with Fink. I recently moved from Fink to MacPorts (version 2.3.3) and the problem appeared when trying to load python scripts but not C programs. I have not tried to fontify other stuff. Finding this thread, I applied successfully the patch indicated here. Phew! I was afraid I would have to keep running Fink and MacPorts in parallel.