Adding virtual destructor breaks C++ ABI compatibility

“Does adding a virtual destructor break ABI compatibility? I have a class hierarchy that already exists that looks like this: [code] The destructor in the parent class doesn't do anything important, so there is no leak when destroying parent. The correct way to do this is to make the destructor virutual to ensure that it gets called. Does adding [code] to the destrcutor in parent break the ABI compatibility? According to the KDE binary compatibility policy page which says in part: You can... Add ”