diff options
| -rw-r--r-- | gdb/ChangeLog | 5 | ||||
| -rw-r--r-- | gdb/PROBLEMS | 15 |
2 files changed, 20 insertions, 0 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 699a31f..0599d7c 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,8 @@ +2003-06-24 Michael Chastain <mec@shout.net> + + * PROBLEMS: Document pr gdb/1091 and pr gdb/1193, + the "constructor breakpoints ignored" bug. + 2003-06-25 David Carlton <carlton@kealia.com> * MAINTAINERS: Update e-mail address. diff --git a/gdb/PROBLEMS b/gdb/PROBLEMS index 84a42b4..7480633 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. |