X-Git-Url: http://drtracing.org/?a=blobdiff_plain;f=gdb%2FPROBLEMS;h=974f4f0108ab5e7b5b64d3d5b48a00a38b53dd55;hb=727605ca75e009d8468bb6378b7d18b774838b2d;hp=74806333035fa78bb3794f6a8ad24c4ce3ba651d;hpb=3c164570275f835fe5d0f0aee13e8bdadecdcc77;p=deliverable%2Fbinutils-gdb.git

diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS
index 7480633303..974f4f0108 100644
--- a/gdb/PROBLEMS
+++ b/gdb/PROBLEMS
@@ -1,21 +1,6 @@
 
-			Known problems in GDB 6.0
+			Known problems in GDB 7.2.50
 
 		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.
+None worth mentioning here.