search for: copiable

...hedBoundary, which explicitly deletes the scoreboard object. Follows that, since both the boundary objects, the original and the copy, hold  a pointer to the same object, a double "delete" is performed. I think this is an issue deriving from the design: if SchedBoundary is designed to be copiable, then solutions may be:     1. The pointer should be wrapped around a smart_ptr (a shared_ptr, since we want to hold a copy)     2.  Define a custom copy-constructor and assign-operator, such that the ScoreBoard object, and not        the pointer, is copied. If SchedBoundary was not designed to...