From 3865c463f57d20d37d3fa8eef90e44c1d87d02ee Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Thu, 13 Jun 2013 10:52:21 -0700 Subject: [PATCH] * DEBUG: Document -fno-omit-frame-pointer. --- etc/ChangeLog | 2 +- etc/DEBUG | 10 +++++----- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/etc/ChangeLog b/etc/ChangeLog index e7fdc25be51..a31c6ff944e 100644 --- a/etc/ChangeLog +++ b/etc/ChangeLog @@ -1,6 +1,6 @@ 2013-06-13 Paul Eggert - * DEBUG: Document -Og. + * DEBUG: Document -Og and -fno-omit-frame-pointer. 2013-06-05 Teodor Zlatanov diff --git a/etc/DEBUG b/etc/DEBUG index a76a60641c9..61a8ee05e27 100644 --- 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 -- 2.39.2