diff options
| author | Paul Eggert <[email protected]> | 2013-06-13 10:04:08 -0700 |
|---|---|---|
| committer | Paul Eggert <[email protected]> | 2013-06-13 10:04:08 -0700 |
| commit | 11169e6f1a9104182176c67623f7f9579aa96997 (patch) | |
| tree | fb3b206115dbd060eb2c8e5033eb6997b1db4cce | |
| parent | ba947bc42f25610df83c3e36d8b7949102054427 (diff) | |
* DEBUG: Document -Og.
| -rw-r--r-- | etc/ChangeLog | 4 | ||||
| -rw-r--r-- | etc/DEBUG | 7 |
2 files changed, 8 insertions, 3 deletions
diff --git a/etc/ChangeLog b/etc/ChangeLog index f80c1b6973..e7fdc25be5 100644 --- a/etc/ChangeLog +++ b/etc/ChangeLog @@ -1,3 +1,7 @@ +2013-06-13 Paul Eggert <[email protected]> + + * DEBUG: Document -Og. + 2013-06-05 Teodor Zlatanov <[email protected]> * NEWS: Document new prog-mode symbol prettify support. @@ -24,8 +24,10 @@ There are several ways to overcome that difficulty, they are all described in the node "Auto-loading safe path" in the GDB user manual. ** When you are trying to analyze failed assertions or backtraces, it -will be essential to compile Emacs either completely without -optimizations (set CFLAGS to "-O0 -g3") or at least (when using GCC) +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 @@ -769,4 +771,3 @@ Local variables: mode: outline paragraph-separate: "[ ]*$" end: - |