I’m running unit tests using Boost::test that starts up Boost threads, shared memory, and message queues. There are multiple tests in the suite.

 

While writing a test it can fail prematurely and leave behind shared memory and message queues. Then when I run the tests again I can have trouble with mutexes, etc that already exist.

 

I am working under Windows but eventually will be moving to Linux.

 

Is there some way (other than rebooting) to force a cleanup of all the system objects that are created in the background? Or even a way of determining what has outlived its usefulness?

 

Thanks.

 

 

 

___________________________________

 

John Davies

Contractor

Home Respiratory Care

Philips Home Healthcare Solutions

1740 Golden Mile Highway

Monroeville, PA 15146

 

Email: john.davies@philips.com

Fax: 724-387-4109

 


The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.