diff options
Diffstat (limited to 'gdb/PROBLEMS')
| -rw-r--r-- | gdb/PROBLEMS | 38 |
1 files changed, 33 insertions, 5 deletions
diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS index d3b4f84..dd90603 100644 --- a/gdb/PROBLEMS +++ b/gdb/PROBLEMS @@ -23,6 +23,30 @@ Fortunately the ARM target, in the GDB's mainline sources, has been updated so people encountering problems should consider downloading a more current GDB (http://www.gnu.org/software/gdb/current). +*** Regressions since gdb 6.0 + +gdb/826: variables in C++ namespaces have to be enclosed in quotes + +When referring to a variable in C++ code that is inside a +namespace, you have to put it inside single quotes. + +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/1505: [regression] gdb prints a bad backtrace for a thread + +When backtracing a thread, gdb doesn't stop until it hits garbage. +This is sensitive to the operating system and thread library. + +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. + 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 @@ -35,6 +59,15 @@ 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). +gdb/1560: Control-C does not always interrupt GDB. + +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. + +*** Regressions since gdb 5.3 + gdb/1091: Constructor breakpoints ignored gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints @@ -52,8 +85,3 @@ 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/1560: Control-C does not always interrupt GDB. -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. |