Commit 11169e6f authored by Paul Eggert's avatar Paul Eggert

* DEBUG: Document -Og.

parent ba947bc4
2013-06-13 Paul Eggert <eggert@cs.ucla.edu>
* DEBUG: Document -Og.
2013-06-05 Teodor Zlatanov <tzz@lifelogs.com>
* 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:
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment