What can cause VTable pointer to be 0xffffdffffddd in Win32 debug build?

Question

I am debugging a defect and have narrowed it down to the vtable pointer for an object being 0xffffdffffddd. This answer indicates that Win32 debug builds will gene

Answer 1

If you start the program, put a break point at where you create the object. Then add a memory break point. This will fire if you overwrite or delete the memory. Well, or change it in any way.

Your object will look correct if the memory isn't overwritten, but your vtable may not be depending on compiler specifics.

It could also be a size problem if you are using inheritance. If you are using any kind of bucket memory or storing objects by anything but the pointer.