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

Okay wow, so I've been programming in c++ for years and never discovered this until now... There are actually magic numbers/magic debug values that you can lookup to see what's going on with your raw pointers while debugging!

See here: In Visual Studio C++, what are the memory allocation representations?

and here: https://en.wikipedia.org/wiki/Magic_number_(programming)#Magic_debug_values