i was trying to create a deque, and when the function that resizes the array is excuted, it crashes with the error from the title, and when i delete the deallocate() it stops happening, what im doing wrong? code: https://pastebin.com/0yHHcLnj

  • @prettydarknwildOP
    link
    2
    edit-2
    1 year ago

    so, that practice of calling .destroy() and then .deallocate() is redundant and error-prone

    • @[email protected]
      link
      fedilink
      2
      edit-2
      1 year ago

      If you develop or debug a container, it is useful to have a special test class for the elements that covers potential container specific errors.

      struct ContainerTester {
      	static int instances;
      	int counter{};
      	int val;
      	
      	ContainerTester() : ContainerTester(0) {}
      	ContainerTester(int val) : val(val)
      	{
      		++counter;
      		++instances;
      	}
      	~ContainerTester() {
      		--counter;
      		--instances;
      		if (counter < 0) std::cout << "multiple destructor calls on same element" << std::endl;
      		if (instances < 0) std::cout << "negative number of instances" << std::endl;
      	}
      };
      
      int ContainerTester::instances{};
      
      std::ostream& operator<<(std::ostream& o, const ContainerTester& c) {return o << c.val;}
      

      If I run your code with ContainerTester instead of int, i get:

      negative number of instances
      negative number of instances
      negative number of instances
      negative number of instances
      negative number of instances
      negative number of instances
      multiple destructor calls on same element
      negative number of instances
      double free or corruption (out)
      segmentation fault
      

      So it’s more obvious that very bad things do happen :)

      Oh and note, that allocator::destroy is deprecated in C++17 and was removed with C++20.

      • @prettydarknwildOP
        link
        11 year ago

        i used tthe tester class with my code removing the .deallocate(), and although it doesnt crash, it still runs the destructor multiple times on the same element, i think its because im just pushing i into the container, and because that constructor creates an implicit conversion between int and ContainerTester, it creates a temporary object that gets destroyed once it is pushed into the deque, am i right?