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