There is a bug (bin/41671) in FreeBSD's gcc that causes it to emit bad
debug information when using the stabs format (which is the default).
-In earlier versions of GDB the effects were rather limited, but
-starting with GDB 5.3 the influence is much more prominent.
+As a result GDB tends to place breakpoints on functions before the
+function prologue, and information about function parameters and local
+variables is lost. In earlier versions of GDB the effects were rather
+limited, but starting with GDB 5.3 the influence is much more
+prominent. As a workaround, compile your code with -gdwarf-2.
hppa2.0-hp-hpux10.20
gdb/455: GDB doesn't build on a FreeBSD 4.4-STABLE system. The
problem is still being investigated.
+
+alpha*-*-osf*
+-------------
+
+gdb/816: When building GDB with GCC 3.0.1, GDB is unable to load a core
+file properly. It generates several errors and warnings regarding
+unhandled core file section types, incorrect endianness, the failure to
+load the registers. Are also incorrectly reported: The program name, the
+cause of the program death, and the call stack at the moment of the
+death. This problem has been reported on alpha-osf4.0f and alpha-osf5.1a.
+To work-around the problem, add -D__digital__ to the CFLAGS when
+building GDB vis:
+
+ $ make CFLAGS='-O2 -D__digital__'
+
+
+i[3456]86-*-linux*
+------------------
+
+gdb/660: gdb does not build with GNU/Linux libc5. The symptom is a
+parse error before `uintptr_t' or an error message about `uintptr_t'.
+Upgrade to glibc 2.1.3 or later, which defines uintptr_t.
+
+gdb/1030: GNU binutils 2.12.1 and earlier versions do not work properly
+with gdb. If you use GNU binutils, upgrade to version 2.13 or later.
+You can check the version of binutils with the command:
+
+ $ ld --version