As is said in the ``C++ Gotchas'' book by S. Dewhurst (gotcha #70), this bug causes unpredictable behaviour.
Chances are you'll just get a call of the base class destructor for the derived class object: a bug. But the compiler may decide to do anything else it feels like (dump core? send nasty email to your boss? sign you up for a lifetime subscription to ``This week in Object-Oriented COBOL''?).