PROBLEMS 4.64 KB
Newer Older
Andrew Cagney's avatar
Andrew Cagney committed
1

2
			Known problems in GDB 6.1.1
Andrew Cagney's avatar
Andrew Cagney committed
3

4
		See also: http://www.gnu.org/software/gdb/bugs/
Andrew Cagney's avatar
Andrew Cagney committed
5

6

7
8
*** Build problems

9
build/1458: compile failed on hpux11
10

11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
GDB has build problems on HP/UX 11 with some versions of the HP
Ansi C compiler.  (GCC works fine).

The problem happens when compiling intl/bindtextdom.c.
The error is:

  cc: "gettextP.h", line 50: error 1000: Unexpected symbol: "SWAP".
  cc: panic 2017: Cannot recover from earlier errors, terminating.
  *** Error exit code 1

This is a problem with the 'inline' keyword in gettextP.h.
The workaround is to disable 'inline' before building gdb:

  export ac_cv_c_inline=no

This problem happens only with some versions of the HP Ansi C compiler.
Versions A.11.01.25171.GP and B.11.11.28706.GP have both been observed
to work; version B.11.11.04 gets the build error and needs the
workaround.

This problem might also happen with other C compilers.
32

33
*** Misc
34

35
gdb/1560: Control-C does not always interrupt GDB.
36

37
38
39
40
41
42
When GDB is busy processing a command which takes a long time to
complete, hitting Control-C does not have the expected effect.
The command execution is not aborted, and the "QUIT" message confirming
the abortion is displayed only after the command has been completed.

*** C++ support
43
44
45
46
47
48
49
50
51
52
53
54
55

gdb/931: GDB could be more generous when reading types C++ templates on input

When the user types a template, GDB frequently requires the type to be
typed in a certain way (e.g. "const char*" as opposed to "const char *"
or "char const *" or "char const*").

gdb/1512: no canonical way to output names of C++ types

We currently don't have any canonical way to output names of C++ types.
E.g. "const char *" versus "char const *"; more subtleties arise when
dealing with templates.

56
57
58
59
60
61
62
63
64
65
66
67
gdb/1516: [regression] local classes, gcc 2.95.3, dwarf-2

With gcc 2.95.3 and the dwarf-2 debugging format, classes which are
defined locally to a function include the demangled name of the function
as part of their name.  For example, if a function "foobar" contains a
local class definition "Local", gdb will say that the name of the class
type is "foobar__Fi.0:Local".

This applies only to classes where the class type is defined inside a
function, not to variables defined with types that are defined somewhere
outside any function (which most types are).

68
69
70
71
72
73
74
75
76
77
78
79
gdb/1588: names of c++ nested types in casts must be enclosed in quotes

You must type
  (gdb) print ('Foo::Bar') x
or
  (gdb) print ('Foo::Bar' *) y
instead of
  (gdb) print (Foo::Bar) x
or
  (gdb) print (Foo::Bar *) y
respectively.

80
81
gdb/1091: Constructor breakpoints ignored
gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints
Andrew Cagney's avatar
Andrew Cagney committed
82

83
84
85
86
87
88
89
90
91
92
93
94
95
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.
96

97
98
*** Stack backtraces

99
100
101
102
103
104
105
GDB's core code base has been updated to use a new backtrace
mechanism.  This mechanism makes it possible to support new features
such DWARF 2 Call Frame Information (which in turn makes possible
backtraces through optimized code).

Since this code is new, it is known to still have a few problems:

106
107
gdb/1505: [regression] gdb prints a bad backtrace for a thread

108
109
110
When backtracing a thread, gdb does not stop when it reaches the
outermost frame, instead continuing until it hits garbage.  This is
sensitive to the operating system and thread library.
111

112
hppa*-*-*
113
114
mips*-*-*

115
116
117
118
The MIPS and HPPA backtrace code has only very recently been updated
to use GDB's new frame mechanism.  At present there are still a few
problems, in particular backtraces through signal handlers do not
work.
119

120
121
122
People encountering problems with these architectures should consult
GDB's web pages and mailing lists (http://www.gnu.org/software/gdb/)
to see if there are updates.
123

124
powerpc*-*-*
125

126
PowerPC architecture support, in 6.1, does not use the new frame code.
127

128
129
130
131
Fortunately, PowerPC architecture support, in GDB's mainline sources,
have been updated.  People encountering problems should consider
downloading a more current snapshot of GDB
(http://www.gnu.org/software/gdb/current/).