gdb/PROBLEMS

   1
   2                         Known problems in GDB 6.0
   3
   4                 See also: http://www.gnu.org/software/gdb/bugs/
   5
   6 mips*-*-*
   7 powerpc*-*-*
   8 sparc*-*-*
   9
  10 GDB's SPARC, MIPS and PowerPC targets, in 6.0, have not been updated
  11 to use the new frame mechanism.
  12
  13 People encountering problems with these targets should consult GDB's
  14 web pages and mailing lists (http://www.gnu.org/software/gdb/) to see
  15 if there is an update.
  16
  17 arm-*-*
  18
  19 GDB's ARM target, in 6.0, has not been updated to use the new frame
  20 mechanism.
  21
  22 Fortunately the ARM target, in the GDB's mainline sources, has been
  23 updated so people encountering problems should consider downloading a
  24 more current GDB (http://www.gnu.org/software/gdb/current).
  25
  26 gdb/1091: Constructor breakpoints ignored
  27 gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints
  28
  29 When gcc 3.x compiles a C++ constructor or C++ destructor, it generates
  30 2 or 3 different versions of the object code.  These versions have
  31 unique mangled names (they have to, in order for linking to work), but
  32 they have identical source code names, which leads to a great deal of
  33 confusion.  Specifically, if you set a breakpoint in a constructor or a
  34 destructor, gdb will put a breakpoint in one of the versions, but your
  35 program may execute the other version.  This makes it impossible to set
  36 breakpoints reliably in constructors or destructors.
  37
  38 gcc 3.x generates these multiple object code functions in order to
  39 implement virtual base classes.  gcc 2.x generated just one object code
  40 function with a hidden parameter, but gcc 3.x conforms to a multi-vendor
  41 ABI for C++ which requires multiple object code functions.