Jerry James writes: If you look at what can be executed (assuming that a wild pointer hasn't overwritten the return address, in which case of course anything can happen), it's the code that outputs the stack trace. So AFAICS, what this means is that if you encounter an assertion failure while autosaving in a fatal error (and that's really the only place you can trigger this AFAICS), you don't get any chance of getting a stack trace at all. Not for the original fatal error and not for the assertion. What is the practical problem with keeping the code as it is? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta