Add information about `-fno-crossjumping' for GCC.

diff --git a/etc/ChangeLog b/etc/ChangeLog
index e357de8121aa5eb0c94c4e156987569ba2b6e512..26ce127e1bdc0c53014a458d25d6afc3d9aef9ca 100644 (file)
--- a/etc/ChangeLog
+++ b/etc/ChangeLog
@@ -1,3 +1,7 @@
+2005-03-01  David Kastrup  <dak@gnu.org>
+
+       * DEBUG: Add information about `-fno-crossjumping' for GCC.
+
 2005-02-14  Lute Kamstra  <lute@gnu.org>
 
        * TODO: Remove battery.el entry (DONE).

diff --git a/etc/DEBUG b/etc/DEBUG
index b242d1d028d308c3f0815750920a7c0a4e7c7584..fe3bde0c3b88784c09d35ad591f2477c4af5bf48 100644 (file)
--- a/etc/DEBUG
+++ b/etc/DEBUG
@@ -1,5 +1,5 @@
 Debugging GNU Emacs
-Copyright (c) 1985, 2000, 2001 Free Software Foundation, Inc.
+Copyright (c) 1985, 2000, 2001, 2005 Free Software Foundation, Inc.
 
    Permission is granted to anyone to make or distribute verbatim copies
    of this document as received, in any medium, provided that the
@@ -20,6 +20,13 @@ document.]
 where the executable was made.  That directory has a .gdbinit file
 that defines various "user-defined" commands for debugging Emacs.
 
+** 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.
+
 ** It is a good idea to run Emacs under GDB (or some other suitable
 debugger) *all the time*.  Then, when Emacs crashes, you will be able
 to debug the live process, not just a core dump.  (This is especially