Preventing Program’s Crash due to a Pure Virtual Function’s Call

Preventing Program’s Crash due to a Pure Virtual Function’s Call

A pure function should never be invoked. However, a buggy program or a buggy compiler can sometimes call a pure virtual function. In general, when a pure virtual function is invoked, the program crashes and you cannot continue debugging it. To prevent the program from crashing, you can implement the pure virtual function. This makes debugging possible even when a pure virtual function is inadvertently called.

 #include using namespace std;class Dog{public:  virtual void Bark()=0; //pure virtual, should never be invoked};  // the following definition ensures that the pure virtual call doesn't crashvoid Dog::Bark(){  cout<<"Dog::Bark called"; }class Beagle : public Dog{public:  virtual void Bark() {cout<<"Beagle"; }};int main(){  Beagle* m_pSnoopy = new Beagle;/* The following should call Beagle::Bark(); a buggy compiler/program calls Dog::bark() instead */  m_pSnoopy->Bark();}

When you have fixed the bug that calls the pure virtual function (or upgrades the faulty compiler), remember to delete the implementation of the pure virtual function.

See also  5 Ways to Improve Customer Experience

About Our Editorial Process

At DevX, we’re dedicated to tech entrepreneurship. Our team closely follows industry shifts, new products, AI breakthroughs, technology trends, and funding announcements. Articles undergo thorough editing to ensure accuracy and clarity, reflecting DevX’s style and supporting entrepreneurs in the tech sphere.

See our full editorial policy.

About Our Journalist