OpenCores
URL https://opencores.org/ocsvn/openrisc/openrisc/trunk

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [gnu-old/] [gdb-6.8/] [gdb/] [PROBLEMS] - Blame information for rev 840

Details | Compare with Previous | View Log

Line No. Rev Author Line
1 24 jeremybenn
 
2
                        Known problems in GDB 6.5
3
 
4
                See also: http://www.gnu.org/software/gdb/bugs/
5
 
6
 
7
*** Build problems
8
 
9
build/1411: build fails on hpux 10.20 and hpux 11.00 with CMA threads
10
 
11
GDB does not build on HP/UX 10.20 or HP/UX 11.00 if the CMA
12
thread package is installed.  The compile error is:
13
 
14
  ../../gdb/hpux-thread.c:222: variable-size type declared outside of any function
15
 
16
This happens only if the CMA thread package is installed.
17
 
18
As a workaround, you can disable support for CMA threads
19
by editing the file gdb/configure.  Find the line:
20
 
21
  if test -f /usr/include/dce/cma_config.h ; then
22
 
23
And replace it with:
24
 
25
  if false ; then
26
 
27
*** Misc
28
 
29
gdb/1560: Control-C does not always interrupt GDB.
30
 
31
When GDB is busy processing a command which takes a long time to
32
complete, hitting Control-C does not have the expected effect.
33
The command execution is not aborted, and the "QUIT" message confirming
34
the abortion is displayed only after the command has been completed.
35
 
36
*** C++ support
37
 
38
gdb/931: GDB could be more generous when reading types C++ templates on input
39
 
40
When the user types a template, GDB frequently requires the type to be
41
typed in a certain way (e.g. "const char*" as opposed to "const char *"
42
or "char const *" or "char const*").
43
 
44
gdb/1512: no canonical way to output names of C++ types
45
 
46
We currently don't have any canonical way to output names of C++ types.
47
E.g. "const char *" versus "char const *"; more subtleties arise when
48
dealing with templates.
49
 
50
gdb/1516: [regression] local classes, gcc 2.95.3, dwarf-2
51
 
52
With gcc 2.95.3 and the dwarf-2 debugging format, classes which are
53
defined locally to a function include the demangled name of the function
54
as part of their name.  For example, if a function "foobar" contains a
55
local class definition "Local", gdb will say that the name of the class
56
type is "foobar__Fi.0:Local".
57
 
58
This applies only to classes where the class type is defined inside a
59
function, not to variables defined with types that are defined somewhere
60
outside any function (which most types are).
61
 
62
gdb/1588: names of c++ nested types in casts must be enclosed in quotes
63
 
64
You must type
65
  (gdb) print ('Foo::Bar') x
66
or
67
  (gdb) print ('Foo::Bar' *) y
68
instead of
69
  (gdb) print (Foo::Bar) x
70
or
71
  (gdb) print (Foo::Bar *) y
72
respectively.
73
 
74
gdb/1091: Constructor breakpoints ignored
75
gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints
76
 
77
When gcc 3.x compiles a C++ constructor or C++ destructor, it generates
78
2 or 3 different versions of the object code.  These versions have
79
unique mangled names (they have to, in order for linking to work), but
80
they have identical source code names, which leads to a great deal of
81
confusion.  Specifically, if you set a breakpoint in a constructor or a
82
destructor, gdb will put a breakpoint in one of the versions, but your
83
program may execute the other version.  This makes it impossible to set
84
breakpoints reliably in constructors or destructors.
85
 
86
gcc 3.x generates these multiple object code functions in order to
87
implement virtual base classes.  gcc 2.x generated just one object code
88
function with a hidden parameter, but gcc 3.x conforms to a multi-vendor
89
ABI for C++ which requires multiple object code functions.
90
 
91
*** Threads
92
 
93
threads/1650: manythreads.exp
94
 
95
On GNU/Linux systems that use the old LinuxThreads thread library, a
96
program rapidly creating and deleting threads can confuse GDB leading
97
to an internal error.
98
 
99
This problem does not occur on newer systems that use the NPTL
100
library, and did not occur with GDB 6.1.
101
 
102
threads/2137: Native Solaris Thread Debugging broken.
103
 
104
Use GDB 6.4 if thread debugging is needed on Solaris.

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.