[Emacs-diffs] trunk r112969: * DEBUG: Document -fno-omit-frame-pointer.

[Paul Eggert]

------------------------------------------------------------
revno: 112969
revision-id: address@hidden
parent: address@hidden
committer: Paul Eggert <address@hidden>
branch nick: trunk
timestamp: Thu 2013-06-13 10:52:21 -0700
message:
  * DEBUG: Document -fno-omit-frame-pointer.
modified:
  etc/ChangeLog                  changelog-20091113204419-o5vbwnq5f7feedwu-1485
  etc/DEBUG                      debug-20091113204419-o5vbwnq5f7feedwu-1486

=== modified file 'etc/ChangeLog'
--- a/etc/ChangeLog     2013-06-13 17:04:08 +0000
+++ b/etc/ChangeLog     2013-06-13 17:52:21 +0000
@@ -1,6 +1,6 @@
 2013-06-13  Paul Eggert  <address@hidden>
 
-       * DEBUG: Document -Og.
+       * DEBUG: Document -Og and -fno-omit-frame-pointer.
 
 2013-06-05  Teodor Zlatanov  <address@hidden>
 

=== modified file 'etc/DEBUG'
--- a/etc/DEBUG 2013-06-13 17:04:08 +0000
+++ b/etc/DEBUG 2013-06-13 17:52:21 +0000
@@ -27,11 +27,11 @@
 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