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 | 6 | |
103a0089 | 7 | *** Misc |
e6beb428 | 8 | |
103a0089 | 9 | gdb/1560: Control-C does not always interrupt GDB. |
e6beb428 | 10 | |
103a0089 AC |
11 | When GDB is busy processing a command which takes a long time to |
12 | complete, hitting Control-C does not have the expected effect. | |
13 | The command execution is not aborted, and the "QUIT" message confirming | |
14 | the abortion is displayed only after the command has been completed. | |
15 | ||
16 | *** C++ support | |
ed47347a | 17 | |
ed47347a MC |
18 | gdb/931: GDB could be more generous when reading types C++ templates on input |
19 | ||
20 | When the user types a template, GDB frequently requires the type to be | |
21 | typed in a certain way (e.g. "const char*" as opposed to "const char *" | |
22 | or "char const *" or "char const*"). | |
23 | ||
ed47347a MC |
24 | gdb/1512: no canonical way to output names of C++ types |
25 | ||
26 | We currently don't have any canonical way to output names of C++ types. | |
27 | E.g. "const char *" versus "char const *"; more subtleties arise when | |
28 | dealing with templates. | |
29 | ||
c6e06ede MC |
30 | gdb/1516: [regression] local classes, gcc 2.95.3, dwarf-2 |
31 | ||
32 | With gcc 2.95.3 and the dwarf-2 debugging format, classes which are | |
33 | defined locally to a function include the demangled name of the function | |
34 | as part of their name. For example, if a function "foobar" contains a | |
35 | local class definition "Local", gdb will say that the name of the class | |
36 | type is "foobar__Fi.0:Local". | |
37 | ||
38 | This applies only to classes where the class type is defined inside a | |
39 | function, not to variables defined with types that are defined somewhere | |
40 | outside any function (which most types are). | |
41 | ||
8c691c7a DC |
42 | gdb/1588: names of c++ nested types in casts must be enclosed in quotes |
43 | ||
44 | You must type | |
45 | (gdb) print ('Foo::Bar') x | |
46 | or | |
47 | (gdb) print ('Foo::Bar' *) y | |
48 | instead of | |
49 | (gdb) print (Foo::Bar) x | |
50 | or | |
51 | (gdb) print (Foo::Bar *) y | |
52 | respectively. | |
53 | ||
e8ac10a6 MC |
54 | gdb/1091: Constructor breakpoints ignored |
55 | gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints | |
e2c9a72c | 56 | |
e8ac10a6 MC |
57 | When gcc 3.x compiles a C++ constructor or C++ destructor, it generates |
58 | 2 or 3 different versions of the object code. These versions have | |
59 | unique mangled names (they have to, in order for linking to work), but | |
60 | they have identical source code names, which leads to a great deal of | |
61 | confusion. Specifically, if you set a breakpoint in a constructor or a | |
62 | destructor, gdb will put a breakpoint in one of the versions, but your | |
63 | program may execute the other version. This makes it impossible to set | |
64 | breakpoints reliably in constructors or destructors. | |
65 | ||
66 | gcc 3.x generates these multiple object code functions in order to | |
67 | implement virtual base classes. gcc 2.x generated just one object code | |
68 | function with a hidden parameter, but gcc 3.x conforms to a multi-vendor | |
69 | ABI for C++ which requires multiple object code functions. | |
589ca796 | 70 | |
103a0089 AC |
71 | *** Stack backtraces |
72 | ||
73 | gdb/1505: [regression] gdb prints a bad backtrace for a thread | |
74 | ||
75 | When backtracing a thread, gdb doesn't stop until it hits garbage. | |
76 | This is sensitive to the operating system and thread library. | |
77 | ||
78 | mips*-*-* | |
79 | powerpc*-*-* | |
80 | sparc*-*-* | |
81 | ||
82 | GDB's SPARC, MIPS and PowerPC targets, in 6.0, have not been updated | |
83 | to use the new frame mechanism. | |
84 | ||
85 | People encountering problems with these targets should consult GDB's | |
86 | web pages and mailing lists (http://www.gnu.org/software/gdb/) to see | |
87 | if there is an update. | |
88 | ||
89 | arm-*-* | |
90 | ||
91 | GDB's ARM target, in 6.0, has not been updated to use the new frame | |
92 | mechanism. | |
93 | ||
94 | Fortunately the ARM target, in the GDB's mainline sources, has been | |
95 | updated so people encountering problems should consider downloading a | |
96 | more current GDB (http://www.gnu.org/software/gdb/current). |