Fix resource leak caused by move ctor/assignment

[elfenpiff]

Required information

All versions

Observed result or behaviour:
The classes:

• unix_domain_socket (fixed by Iox #381 Fix flooding the command line and resource leak #550)
• shared_memory
• memory_map
• GenericRAII

are not cleaning up the resources while performing move. This could lead to a resource leak when for instance the following pseudo code is executed.

SharedMemory mySharedMemory; // create a shared memory file A
SharedMemory anotherSharedMemory; // create a shared memory file B

mySharedMemory = std::move(anotherSharedMemory); // mySharedMemory takes ownership of B without releasing A

// at this point the shared memory file A is leaked

Classes with correct move resource handling:

• Semaphore
• MessageQueue
• optional
• variant

Handle undefined state:

• optional
• expected

creation pattern:

• shared_memory
• shared_memory_object
• memory_map

Fix incorrect move CTor/assigned in all classes derived from DesignPattern::Creation
According to: https://isocpp.org/wiki/faq/assignment-operators every move ctor/assignment operator has to be implemented like

Derived& Derived::operator= (Derived&& d)
{
  // self-assignment is not allowed in move assignment
  Base::operator= (std::move(d));
  // Do the rest of your assignment operator here...
  return *this;
}

• shared_memory
• shared_memory_object
• memory_map
• semaphore
• message_queue
• unix_domain_socket
• Write a detailed documentation how to use the creation pattern correctly - especially the assignment operator part!

Fix sighandler

• Write mini sigaction abstraction and put it into utils to remove the 5 lines of code.
• Use posix::SignalHandler everywhere

Details

• Consider this discussion

[elfenpiff]

@sschnitzer Thank you for finding this!