gdb/PROBLEMS

   1
   2                         Known problems in GDB 5.3
   3
   4                 See also: http://www.gnu.org/software/gdb/bugs/
   5
   6
   7 *-*-freebsd*
   8 ---------------
   9
  10 Due to a kernel bug (kern/35175), detaching from an attached process
  11 will very likely cause the process to be stop or die with a Trace/BPT
  12 trap.
  13
  14
  15 i386-*-freebsd[34]*
  16 -------------------
  17
  18 There is a bug (bin/41671) in FreeBSD's gcc that causes it to emit bad
  19 debug information when using the stabs format (which is the default).
  20 As a result GDB tends to place breakpoints on functions before the
  21 function prologue, and information about function parameters and local
  22 variables is lost.  In earlier versions of GDB the effects were rather
  23 limited, but starting with GDB 5.3 the influence is much more
  24 prominent.  As a workaround, compile your code with -gdwarf-2.
  25
  26
  27 hppa2.0-hp-hpux10.20
  28 --------------------
  29
  30 gdb/487: The top level make files used to build GDB are not compatible
  31 with HP/UX make.  As a workaround, use GNU make.
  32
  33 gdb/486: The HP/UX C compiler defaults to K&R mode but GDB only builds
  34 with an ISO C compiler.  The top level configuration incorrectly sets
  35 CC to `cc' instead of `cc -Ae'.  As a workaround, the correct compiler
  36 can be specified as part of the configuration vis:
  37
  38     $  'CC=cc -Ae' ./configure
  39
  40
  41 s390*-*-*
  42 ---------
  43
  44 gdb/513: GDB does not build on s390 GNU/Linux.  The problem should be
  45 fixed in more recent sources.
  46
  47
  48 i386-*-freebsd4.4*
  49 ------------------
  50
  51 gdb/455: GDB doesn't build on a FreeBSD 4.4-STABLE system.  The
  52 problem is still being investigated.
  53
  54 alpha*-*-osf*
  55 -------------
  56
  57 gdb/816: When building GDB with GCC 3.0.1, GDB is unable to load a core
  58 file properly. It generates several errors and warnings regarding
  59 unhandled core file section types, incorrect endianness, the failure to
  60 load the registers. Are also incorrectly reported: The program name, the
  61 cause of the program death, and the call stack at the moment of the
  62 death. This problem has been reported on alpha-osf4.0f and alpha-osf5.1a.
  63 To work-around the problem, add -D__digital__ to the CFLAGS when
  64 building GDB vis:
  65
  66     $ make CFLAGS='-O2 -D__digital__'
  67
  68
  69 *-*-linux*-gnu*
  70 ---------------
  71
  72 gdb/725: Crash using debug target and regcaches (in 5.3 branch?)]].
  73 When debugging a threaded application, the maintainer command `(gdb)
  74 set debug target 1' causes GDB to to into an infinite loop.  To
  75 work-around this problem, avoid using the maintainer command `(gdb)
  76 set debug target 1' when debugging a threaded application.
  77