I have a problem with the latest 21.5 CVS source code under native win32. Perl files make XEmacs crash when fontified. I have posted a backtrace of the problem where it appears that some buf structure has a null member: buf->text = 0 ! xemacs.exe!membpos_to_bytebpos(buffer * buf=0x014a3b98, long x=0x01463e90) Line 706 + 0xc C xemacs.exe!signal_syntax_table_extent_changed(extent * extent=0x00af61c0) Line 420 + 0xb C xemacs.exe!signal_single_extent_changed(extent * extent=0x00af61c0, long property=0x0149db08, long old_start=0x00000000, long old_end=0x00000000) Line 1777 C xemacs.exe!signal_extent_changed(extent * extent=0x00af61c0, long property=0x0149db08, long old_start=0x00000000, long old_end=0x00000000, int descendants_too=0x00000001) Line 1818 C xemacs.exe!signal_extent_property_changed(extent * extent=0x00af61c0, long property=0x0149db08, int descendants_too=0x00000001) Line 1825 C xemacs.exe!Fset_extent_property(long extent=0x00af61c0, long property=0x0149db08, long value=0x03cf3990) Line 5722 C Here is the lisp backtrace for the same problem if it can help: Signaling: (invalid-argument "Marker does not point anywhere (buf has no text)") remove-text-properties(1 2140 (syntax-type t in-pod t syntax-table t cperl-postpone t syntax-subtype t rear-nonsticky t indentable t)) cperl-find-pods-heres(1 2140 t nil t) cperl-fontify-syntaxically(2140) font-lock-fontify-syntactic-keywords-region(1558 2140) font-lock-default-fontify-region(1558 2140 nil) font-lock-fontify-region(1558 2140) lazy-shot-fontify-internal(#<buffer "l2hconf.pin"> 1558 2071 t "") lazy-shot-lock-extent(#<destroyed extent> nil) lazy-shot-redisplay-function(#<destroyed extent>) I got it by removing the assert and replacing it by a lisp signal. -- Fabrice