blob: 77deedc057ee5c20c82e1e25fa52a6801ca58e62 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
|
Known problems in GDB 6.0
See also: http://www.gnu.org/software/gdb/bugs/
gdb/1091: Constructor breakpoints ignored
gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints
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.
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.
gdb/1322: "internal-error: sect_index_text not initialized" after printing a java type
When gdb debugs a Java program which uses shared libraries, it can
generate this internal error.
If you get this error when debugging Java, you can try working around
the problem by relinking your program with no shared libraries at all
(even the standard C library). With the GNU linker, use the "-static"
argument to do this.
You can also try this patch for gdb:
http://sources.redhat.com/ml/gdb-prs/2003-q3/msg00190.html
|
