[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: where's --nofork gone?
From:       Joachim Eibl <joachim.eibl () gmx ! de>
Date:       2004-05-06 20:34:37
Message-ID: 200405062234.37461.joachim.eibl () gmx ! de
[Download RAW message or body]

> If anyone knows better, please tell us about. I am still curious.

I found something about the current gdb-6.1. So the bug is still with us. See 
below.

Cheers,
Joachim

Quoting from:
http://linuxtoday.com/developer/mailprint.php3?action=pv&ltsn=2004-04-19-003-26-NW-SW-RL
...
Known problems in GDB 6.1 
...
gdb/1091: Constructor breakpoints ignored
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=1091
gdb/1193: g++ 3.3 creates multiple constructors: gdb 5.3 can't set breakpoints 
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=1193

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. 

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]