Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

The "what were they thinking" department



Jerry Feldman writes:

> I think this is really the issue. We now have a rather complex yet
> powerful language. WRT: GDB&GCC, this looks like a finger-pointing
> issue. GDB wants it fixed in GCC, and GCC wants it fixed in GDB. 

Not that I want to get into a flame-war or anything, but I think that
the GDB folks are going to have to fix this.

My reasoning:  GCC emits multiple functions to implement ctors so it
can implement virtual base classes in such a way that the code is
compatable with the new C++ ABI.  However, other compilers can
generate code like this as well. Since gdb purports to support C++
binaries produced by compilers other than the gcc family, gdb will
have to be enhanced in this area.

> I actually encountered this very same problem myself the other day. 

Hmm.  This explains a problem I had a while ago too.  Damn...

Regards,

--kevin
-- 
Kevin D. Clark / Cetacean Networks / Portsmouth, N.H. (USA)
cetaceannetworks.com!kclark (GnuPG ID: B280F24E)
alumni.unh.edu!kdc





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org