Details
Critical Description
Whenever a thread is created in my receiver program, The use of the activemq::library::ActiveMQCPP::shutdownLibrary(); causes a core dump after my return 0; statement
It does not happen on my sender after applying patch for a similar issue, and this is almost identical, so I can not find the difference.
The cause is trying to lock a null mutex in the function Threading.cpp::attachToCurrentThread(). This gets called only once in my sender program, during the activemq::library::ActiveMQCPP::initializeLibrary(); call, but it gets called twice in my receiver program, once in the same place and then after the return 0; line. At that point library->globalLock is NULL.
Will attach my source in a moment, but I have literally taken it down to the bare minimum so that it has no function.
