Stephen J. Turnbull, XEmacs 21.5 Beta Engineer wrote:
* XEmacs 21.5.25 "eggplant" is released.
Two crashes have been fixed, in Xft related to fonts with non-ASCII
names
and in the syntax cache triggered by the combination of cperl-mode and
completion.el. Other minor fixes and improvements are listed below, with
detailed descriptions in the ChangeLogs.
Both 21.5.24 and 21.5.25 crash for me at startup when run in an Asian locale.
This is on a Fedora Core 4 x86-64 box if it matters.
Is this a known problem?
Jens
xemacs-21.5.25% LANG=ja_JP.UTF-8 ./src/xemacs -vanilla
initialized metrics ascent 14 descent 3 width 8 height 16
initialized font monospace-12
checking if Kochi Gothic-12:hintstyle=3 handles English
Xft font Kochi Gothic-12:hintstyle=3 doesn't support en
checking if Kochi Mincho-12:hintstyle=3 handles English
Xft font Kochi Mincho-12:hintstyle=3 doesn't support en
Fatal error: assertion failed, file frame-x.c, line 281, ABORT()
Fatal error (6).
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 that won't work, send ordinary
email to `xemacs-beta(a)xemacs.org'. *MAKE SURE* to include this entire
output from this crash, especially including the Lisp backtrace, as well as
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 /home/petersen/src/xemacs/xemacs-21.5.25/src/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:
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# bind (frame-being-created)
make-frame(nil #<x-device on ":0.0" 0x3176a>)
frame-initialize()
# bind (debugger debug-on-error command-line-args-left)
command-line()
# (condition-case ... . ((t (byte-code " ��" [error-data data nil] 1))))
# bind (error-data)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)