This is the mail archive of the
cygwin
mailing list for the Cygwin project.
xemacs crash when fontifying files
- From: Will Parsons <varro at nodomain dot invalid>
- To: cygwin at cygwin dot com
- Date: Thu, 12 Feb 2015 23:17:01 +0000 (UTC)
- Subject: xemacs crash when fontifying files
- Authentication-results: sourceware.org; auth=none
- Reply-to: gyliamos at gmail dot com
I've recently noticed that xemacs will crash if one attempts to turn on
syntax highlighting via turn-on-font-lock (even started with the -q option),
but only if run under X. (If X is not running, there is no problem.) The
crash causes the following to print:
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 recdabas.c..." 0 nil)
# bind (frame value message label)
display-progress-feedback(font-lock "Fontifying recdabas.c..." 0)
# bind (str)
# (unwind-protect ...)
# bind (args value fmt label)
progress-feedback-with-label(font-lock "Fontifying %s..." 0 "recdabas.c")
# bind (maybe-loudly end beg)
font-lock-default-unfontify-region(1 32102 t)
# bind (loudly end beg)
font-lock-unfontify-region(1 32102 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(1)
#<compiled-function nil "...(4)" [font-lock-mode 1] 2 ("/usr/share/xemacs-21.4.23/lisp/font-lock.elc" . 36897) nil>()
call-interactively(turn-on-font-lock)
command-execute(turn-on-font-lock 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 (core dumped)
Although I don't use XEmacs a lot, I do have it configured as the editor to
use for entering configuration control check-in messages, so I think the
problem must be fairly recent or I would have noticed it before.
(If this problem is better posted to the Cygwin-xfree list, let me know and
I'll post it there.)
--
Will
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple