* sparc64-tdep.h (sparc64_regnum): Fix comment.
[deliverable/binutils-gdb.git] / gdb / PROBLEMS
CommitLineData
e2c9a72c 1
f2c06f52 2 Known problems in GDB 6.0
e2c9a72c 3
36cc83a3 4 See also: http://www.gnu.org/software/gdb/bugs/
e2c9a72c 5
e8ac10a6
MC
6gdb/1091: Constructor breakpoints ignored
7gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints
e2c9a72c 8
e8ac10a6
MC
9When gcc 3.x compiles a C++ constructor or C++ destructor, it generates
102 or 3 different versions of the object code. These versions have
11unique mangled names (they have to, in order for linking to work), but
12they have identical source code names, which leads to a great deal of
13confusion. Specifically, if you set a breakpoint in a constructor or a
14destructor, gdb will put a breakpoint in one of the versions, but your
15program may execute the other version. This makes it impossible to set
16breakpoints reliably in constructors or destructors.
17
18gcc 3.x generates these multiple object code functions in order to
19implement virtual base classes. gcc 2.x generated just one object code
20function with a hidden parameter, but gcc 3.x conforms to a multi-vendor
21ABI for C++ which requires multiple object code functions.
This page took 0.190909 seconds and 4 git commands to generate.