21.5 crash in Gnus

Hi folks, Still trying to get my XEmacs + Gnus setup going. While customizing a group in XEmacs 21.5, I got the following crash. The stuff about simplified Chinese is bogus, by the way. I was looking at an email sent from a Windows user, so it may be some Microsoft brain damage, but was definitely written in English. Since I can't yet send email with XEmacs, this is coming to you courtesy of Evolution. Also, I regret to say that I haven't unlimited corefilesize, so there is no core file. I'll fix that right away and see if I can provoke this crash again. $ xemacs & checking if Lucida Sans Typewriter-12:hintstyle=3 handles simplified Chinese Xft font Lucida Sans Typewriter-12:hintstyle=3 doesn't support zh-CN checking if Nimbus Roman No9 L-12:hintstyle=3 handles simplified Chinese Xft font Nimbus Roman No9 L-12:hintstyle=3 doesn't support zh-CN Fatal error: assertion failed, file /home/james/xemacs/xemacs-21.5/src/alloc.c, line 398, !regex_malloc_disallowed 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&#39;. *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 /usr/local/test/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: # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) ("(in char-byte conversion)" "[internal]") # (unwind-protect ...) # (unwind-protect ...) re-search-forward("\\b\\(\\(www\\.\\|\\(s?https?\\|ftp\\|file\\|gopher\\|nntp\\|news\\|telnet\\|wais\\|mailto\\|info\\):\\)\\(//[-a-z0-9_.]+:[0-9]*\\)?\\([-a-z0-9_=!?#$＠~%&*+\\/:;.,]\\|\\w\\)+\\([-a-z0-9_=#$＠~%&*+\\/]\\|\\w\\)\\)" nil t) # bind (inhibit-read-only inhibit-point-motion-hooks case-fold-search alist beg entry regexp) # (unwind-protect ...) # bind (force) gnus-article-add-buttons() # (unwind-protect ...) # bind (--dolist-temp--8834 elem length alist article-goto-body-goes-to-point-min-p treated-type highlightp val elem type total-parts part-number condition) gnus-treat-article(nil 1 1) # (unwind-protect ...) # bind (display e b type name handle inhibit-read-only handles) # (unwind-protect ...) # bind (ssw8827) # (unwind-protect ...) # bind (ihandles) gnus-display-mime() # bind (gnus-article-buffer buffer-read-only inhibit-read-only) gnus-article-prepare-display() # (unwind-protect ...) # bind (result group gnus-tmp-internal-hook summary-buffer gnus-article) # (unwind-protect ...) # bind (header all-headers article) gnus-article-prepare(2 nil) # bind (all-header article) gnus-summary-display-article(2) # bind (article article-window endp stop circular lines) gnus-summary-next-page(nil) # bind (command-debug-status) call-interactively(gnus-summary-next-page) (dispatch-event "[internal]") # (condition-case ... . error) # (catch top-level ...) Regards, -- Jerry James, Assistant Professor Email: Jerry.James(a)usu.edu Computer Science Dept. Web: http://www.cs.usu.edu/~jerry/ Utah State University