Hi, I scanned some of the bug reports in the BugTracking system (BTW it's amazing how many people use and crash XEmacs, we could make a list of quite some Fortune500 companies). My favourite is the one from the lady at amazon who launched xemacs unintentionally, got a crash and was now worried that she had broken something. :-) There are quite a lot of people reporting crashes in skip-syntax-backward, all on Sparc based Systems. We had a discussion about this some time ago and I came to the conclusion that it is a bug in gcc2.8.1 (and some egcs versions) on sparc. This shows up if compiled with at least -O2 (which is the default, isn't it?). for details and a crash recipe see: http://www.xemacs.org/list-archives/xemacs-beta/9807/msg00768.html It can be fixed by compiling (at least search.c) with an additional -fno-schedule-insns. I think this will hit *many* of our users with the release of 21.0, as nowadays gcc >=2.8 is pretty widespread. We should write an entry for PROBLEMS (in fact I will do that later today!), but I think almost nobody reads that file anyway. This will give us a nice answer for comp.emacs.xemacs to the crash reports ('we told you so!'), but doesn't prevent the crashes. Isn't there anything else we can do? like, some smart logic in configure that screams at the user when he's trying such a build or some nifty #pragmas in search.c to work around this or a fix for gcc... Any ideas? Gunnar