* DEBUG: Document -fno-omit-frame-pointer.

diff --git a/etc/ChangeLog b/etc/ChangeLog
index e7fdc25be51ee4f855fe3a933f0fa6afe31ed0e4..a31c6ff944e1e17242eeb87c3c115b18e432b3de 100644 (file)
--- a/etc/ChangeLog
+++ b/etc/ChangeLog
@@ -1,6 +1,6 @@
 2013-06-13  Paul Eggert  <eggert@cs.ucla.edu>
 
-       * DEBUG: Document -Og.
+       * DEBUG: Document -Og and -fno-omit-frame-pointer.
 
 2013-06-05  Teodor Zlatanov  <tzz@lifelogs.com>
 

diff --git a/etc/DEBUG b/etc/DEBUG
index a76a60641c9dd02f000defda7a66a915f5eb64ce..61a8ee05e272e7cafa97a806ffa49cd7b6f0cc94 100644 (file)
--- a/etc/DEBUG
+++ b/etc/DEBUG
@@ -27,11 +27,11 @@ described in the node "Auto-loading safe path" in the GDB user manual.
 is essential to compile Emacs with flags suitable for debugging.
 With GCC 4.8 or later, you can invoke 'make' with CFLAGS="-Og -g3".
 With older GCC or non-GCC commpilers, you can use CFLAGS="-O0 -g3".
-With GCC and higher optimization levels such as -O2, at least compile
-with the -fno-crossjumping option in CFLAGS.  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.
+With GCC and higher optimization levels such as -O2, the
+-fno-omit-frame-pointer and -fno-crossjumping options are often
+essential.  The latter prevents GCC from using 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