"Stephen J. Turnbull" <stephen(a)xemacs.org&gt; writes: ** When you are trying to analyze failed assertions, it will be essential to compile Emacs either completely without optimizations or at least (when using GCC) with the -fno-crossjumping option. Failure to do so may make the compiler recycle the same abort call for all assertions in a given function, rendering the stack backtrace useless for identifying the specific failed assertion. I have tried to convince gcclib developers _not_ to declare the abort function as _noreturn_ since its sole function over exit(1) is to create a core dump and/or let a break point be set, and this is utterly useless if the compiler assumes that it can trash the stack and does not need to retain a recognizable return address. It is useless to try arguing with Drepper. abort does not return, so the declaration is noreturn, period. No changes that would cause less "optimization" to occur are to be done. So if you want to debug anything using assertions, use -fno-crossjumping when compiling, or your stack frame is a piece of junk by the time you hit your breakpoint, and you'll likely waste days figuring out why an assertion triggered at a code point that actually never got executed. -- David Kastrup _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta