Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m analyzing an access violation in our application that occurs because it tries to call a virtual function on an object whose virtual function table points to 0. So I’d like to know at what points in an object’s lifetime is the virtual function table pointer not set or explicitly set to zero?
(We use Visual C++ 10 as a compiler.)
The vtable pointer will never be 0 while the object is in a valid state. During construction and destruction, while the object has a dynamic type of an abstract base class, the vtable will point to the abstract base class vtable, which will include pure virtual functions, but the vtable pointer itself will still be non-zero.
The only time the vtable pointer can be zero is before construction or after destruction.