; * etc/DEBUG: Add link to GCC bug #78685.

(cherry picked from commit d56e5ba97ee49bc7d82ad21e35ac8fbc21a0b0e1)

diff --git a/etc/DEBUG b/etc/DEBUG
index ee920a6e89c05e20c3c309f327c10c69dbb9d4a0..0d149534d19c22725c4b136ca2dc0eed374bd841 100644 (file)
--- a/etc/DEBUG
+++ b/etc/DEBUG
@@ -20,7 +20,7 @@ such as --prefix):
     CFLAGS='-O0 -g3'
 
 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
+in the case that the -Og compiler option is used.[1]  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.
@@ -38,6 +38,9 @@ this below under "Debugging Emacs redisplay problems".
 Emacs needs not be installed to be debugged, you can debug the binary
 created in the 'src' directory.
 
+[1]  gcc's -Og has some known problems and limitations, documented here:
+     https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78685
+
 *** Configuring GDB
 
 To start GDB to debug Emacs, you can simply type "gdb ./emacs RET" at