A class that owns a resource through a raw pointer has to say what copying, moving and destroying mean. The rule of three: if you write one of the destructor, the copy constructor and the copy assignment, you almost certainly need all three; with the two moves it becomes the rule of five. The compiler's default copy copies the pointer, not what it points at, so two objects end up sharing one array and both free it.
The better rule is the rule of zero: hold resources in members that already manage themselves (std::vector, std::string, std::unique_ptr) and write none of the five. The defaults then do the right thing.
When you do write them, two techniques help. Copy, then swap builds the new state in a separate object and swaps it in only when it is complete, so a failure halfway leaves the original untouched: the strong guarantee. And a type that must have a single owner, like a session handle, deletes its copy operations and writes only the moves.
No destructor and no copy code: copies of a Ladder are independent because the vector copies itself.