- Known problems in GDB 5.1.1
+ Known problems in GDB 6.1
-See also the bug database http://www.gnu.org/software/gdb/bugs/
+ See also: http://www.gnu.org/software/gdb/bugs/
-Contrary to the GDB 5.1.1 announcement, the update did not contain
-fixes to a i386 floating point problem. The latest sources do contain
-the fix and it will be included in GDB 5.2.
+*** Build problems
+build/1458: comple failed on hpux11
- Known problems in GDB 5.1
+GDB 6.1 is known to have build problems on HP/UX 11.00 using the
+vendor supplied compilers (GDB does build on HP/UX 11.11, and using
+GCC).
+*** Misc
-hppa2.0-hp-hpux10.20
+gdb/1560: Control-C does not always interrupt GDB.
-Due to a problem (conflicting types) with libiberty/regex.c, GDB 5.1
-does not build on HP/UX 10.20 when using the HP supplied compiler.
+When GDB is busy processing a command which takes a long time to
+complete, hitting Control-C does not have the expected effect.
+The command execution is not aborted, and the "QUIT" message confirming
+the abortion is displayed only after the command has been completed.
-Due to bit rot, GDB 5.1 does not work on HP/UX 10.20 when built with
-GCC.
+*** C++ support
+gdb/931: GDB could be more generous when reading types C++ templates on input
-hppa2.0w-hp-hpux11.00
+When the user types a template, GDB frequently requires the type to be
+typed in a certain way (e.g. "const char*" as opposed to "const char *"
+or "char const *" or "char const*").
-Due to a problem with ltconfig and long argument lines, GDB 5.1 does
-not configure on HP/UX 11.00.
+gdb/1512: no canonical way to output names of C++ types
+We currently don't have any canonical way to output names of C++ types.
+E.g. "const char *" versus "char const *"; more subtleties arise when
+dealing with templates.
-alpha-dec-osf5.1
+gdb/1516: [regression] local classes, gcc 2.95.3, dwarf-2
-GDB 5.1 has a number of problems on this platform (Ref PR gdb/237). A
-GDB 5.1 built with ``CC="cc -DUSE_LDR_ROUTINES"'' is reported to work
-much better.
+With gcc 2.95.3 and the dwarf-2 debugging format, classes which are
+defined locally to a function include the demangled name of the function
+as part of their name. For example, if a function "foobar" contains a
+local class definition "Local", gdb will say that the name of the class
+type is "foobar__Fi.0:Local".
+This applies only to classes where the class type is defined inside a
+function, not to variables defined with types that are defined somewhere
+outside any function (which most types are).
-alpha-dec-osf4.0e
+gdb/1588: names of c++ nested types in casts must be enclosed in quotes
-GDB 5.1 is known to have problems on this platform (encounters an
-internal error in the symbol table reader).
+You must type
+ (gdb) print ('Foo::Bar') x
+or
+ (gdb) print ('Foo::Bar' *) y
+instead of
+ (gdb) print (Foo::Bar) x
+or
+ (gdb) print (Foo::Bar *) y
+respectively.
+gdb/1091: Constructor breakpoints ignored
+gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints
-sparcv9-sun-solaris2.8
+When gcc 3.x compiles a C++ constructor or C++ destructor, it generates
+2 or 3 different versions of the object code. These versions have
+unique mangled names (they have to, in order for linking to work), but
+they have identical source code names, which leads to a great deal of
+confusion. Specifically, if you set a breakpoint in a constructor or a
+destructor, gdb will put a breakpoint in one of the versions, but your
+program may execute the other version. This makes it impossible to set
+breakpoints reliably in constructors or destructors.
-There are known problems with building GDB 5.1 using GCC 3.0.x for the
-64 bit SPARC target (bad code gen). You could try a development
-version of GCC.
+gcc 3.x generates these multiple object code functions in order to
+implement virtual base classes. gcc 2.x generated just one object code
+function with a hidden parameter, but gcc 3.x conforms to a multi-vendor
+ABI for C++ which requires multiple object code functions.
+*** Stack backtraces
-i586-sco-sysv5uw7.1.1
+GDB's core code base has been updated to use a new backtrace
+mechanism. This mechanism makes it possible to support new features
+such DWARF 2 Call Frame Information (which in turn makes possible
+backtraces through optimized code).
-There are known problems with GDB 5.1's thread support on this
-platform. Non-threaded programs should work.
+Since this code is new, it is known to still have a few problems:
+gdb/1505: [regression] gdb prints a bad backtrace for a thread
-*-*-*
+When backtracing a thread, gdb does not stop when it reaches the
+outermost frame, instead continuing until it hits garbage. This is
+sensitive to the operating system and thread library.
-GDB 5.1 assumes that the host C compiler implemends alloca(). GCC is
-one such compiler. This problem should be fixed on the trunk.
+hppa*-*-*
+mips*-*-*
+
+The MIPS and HPPA backtrace code has only very recently been updated
+to use GDB's new frame mechanism. At present there are still a few
+problems, in particular backtraces through signal handlers do not
+work.
+
+People encountering problems with these architectures should consult
+GDB's web pages and mailing lists (http://www.gnu.org/software/gdb/)
+to see if there are updates.
+
+powerpc*-*-*
+
+PowerPC architecture support, in 6.1, does not use the new frame code.
+
+Fortunately, PowerPC architecture support, in GDB's mainline sources,
+have been updated. People encountering problems should consider
+downloading a more current snapshot of GDB
+(http://www.gnu.org/software/gdb/current/).
projects / deliverable / binutils-gdb.git / blobdiff