From: Sean Whitton Date: Thu, 24 Apr 2025 12:14:36 +0000 (+0800) Subject: ; * etc/DEBUG: Say that debugging code compiled w/ -Og can be hard. X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=14c91dc3baf31e0b00ecd2fe074a862706dbcc9c;p=emacs.git ; * etc/DEBUG: Say that debugging code compiled w/ -Og can be hard. (cherry picked from commit 62b284f91530952b248884f0de2f0dbd7b97b26c) --- diff --git a/etc/DEBUG b/etc/DEBUG index b95ea7e7e8c..ee920a6e89c 100644 --- a/etc/DEBUG +++ b/etc/DEBUG @@ -19,11 +19,11 @@ such as --prefix): ./configure --enable-checking='yes,glyphs' --enable-check-lisp-object-type \ CFLAGS='-O0 -g3' -The -O0 flag is important, as debugging optimized code can be hard. -If the problem happens only with optimized code, you may need to -enable optimizations. If that happens, try using -Og first instead of --O2, as -Og disables some optimizations that make debugging some code -exceptionally hard. +The -O0 flag is important, as debugging optimized code can be hard, even +in the case that the -Og compiler option is used. If the problem +happens only with optimized code, you may need to enable optimizations. +If that happens, try using -Og first instead of -O2, as -Og disables +some optimizations that make debugging some code exceptionally hard. Older versions of GCC may need more than just the -g3 flag. For more, search for "analyze failed assertions" below.