2004-03-16 Michael Chastain <mec.gnu@mindspring.com>
[deliverable/binutils-gdb.git] / gdb / PROBLEMS
1
2 Known problems in GDB 6.1
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 *** Regressions since gdb 6.0
27
28 gdb/826: variables in C++ namespaces have to be enclosed in quotes
29
30 When referring to a variable in C++ code that is inside a
31 namespace, you have to put it inside single quotes.
32
33 gdb/931: GDB could be more generous when reading types C++ templates on input
34
35 When the user types a template, GDB frequently requires the type to be
36 typed in a certain way (e.g. "const char*" as opposed to "const char *"
37 or "char const *" or "char const*").
38
39 gdb/1505: [regression] gdb prints a bad backtrace for a thread
40
41 When backtracing a thread, gdb doesn't stop until it hits garbage.
42 This is sensitive to the operating system and thread library.
43
44 gdb/1512: no canonical way to output names of C++ types
45
46 We currently don't have any canonical way to output names of C++ types.
47 E.g. "const char *" versus "char const *"; more subtleties arise when
48 dealing with templates.
49
50 gdb/1516: [regression] local classes, gcc 2.95.3, dwarf-2
51
52 With gcc 2.95.3 and the dwarf-2 debugging format, classes which are
53 defined locally to a function include the demangled name of the function
54 as part of their name. For example, if a function "foobar" contains a
55 local class definition "Local", gdb will say that the name of the class
56 type is "foobar__Fi.0:Local".
57
58 This applies only to classes where the class type is defined inside a
59 function, not to variables defined with types that are defined somewhere
60 outside any function (which most types are).
61
62 gdb/1560: Control-C does not always interrupt GDB.
63
64 When GDB is busy processing a command which takes a long time to
65 complete, hitting Control-C does not have the expected effect.
66 The command execution is not aborted, and the "QUIT" message confirming
67 the abortion is displayed only after the command has been completed.
68
69 *** Regressions since gdb 5.3
70
71 gdb/1091: Constructor breakpoints ignored
72 gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints
73
74 When gcc 3.x compiles a C++ constructor or C++ destructor, it generates
75 2 or 3 different versions of the object code. These versions have
76 unique mangled names (they have to, in order for linking to work), but
77 they have identical source code names, which leads to a great deal of
78 confusion. Specifically, if you set a breakpoint in a constructor or a
79 destructor, gdb will put a breakpoint in one of the versions, but your
80 program may execute the other version. This makes it impossible to set
81 breakpoints reliably in constructors or destructors.
82
83 gcc 3.x generates these multiple object code functions in order to
84 implement virtual base classes. gcc 2.x generated just one object code
85 function with a hidden parameter, but gcc 3.x conforms to a multi-vendor
86 ABI for C++ which requires multiple object code functions.
87
This page took 0.047436 seconds and 5 git commands to generate.