summaryrefslogtreecommitdiff
path: root/gdb/PROBLEMS
diff options
context:
space:
mode:
authorMichael Chastain <mec@google.com>2003-06-26 16:22:59 +0000
committerMichael Chastain <mec@google.com>2003-06-26 16:22:59 +0000
commite8ac10a6d24baaa047da8824433a6393cc8af7c3 (patch)
tree2f3239deaa430330a2cb739e5709a3c1bf33bc4e /gdb/PROBLEMS
parentf40ab5dda0a635c63367d879d2bca7bc36240966 (diff)
downloadbinutils-gdb-e8ac10a6d24baaa047da8824433a6393cc8af7c3.tar.gz
2003-06-24 Michael Chastain <mec@shout.net>
* PROBLEMS: Document pr gdb/1091 and pr gdb/1193, the "constructor breakpoints ignored" bug.
Diffstat (limited to 'gdb/PROBLEMS')
-rw-r--r--gdb/PROBLEMS15
1 files changed, 15 insertions, 0 deletions
diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS
index 84a42b48911..74806333035 100644
--- a/gdb/PROBLEMS
+++ b/gdb/PROBLEMS
@@ -3,4 +3,19 @@
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.