win32 shared_mutex constructor leaks on exceptions

[phrosty@…]

shared_mutex's contructor contains three calls to create_anonymous_semaphore(), each of which can throw. If one of these throws, the unprotected handles of the previous ones will leak.

[viboes]

Thanks for this report. I will try to solve it soon.

[viboes]

In order to avoid a chained try-catch a no_throw create_anonymous_semaphore_nothrow function can be used like in

            if (!semaphores[exclusive_sem])
            {
              detail::win32::release_semaphore(semaphores[unlock_sem],LONG_MAX);
              boost::throw_exception(thread_resource_error());
            }
            upgrade_sem=detail::win32::create_anonymous_semaphore_nothrow(0,LONG_MAX);
            if (!upgrade_sem)
            {
              detail::win32::release_semaphore(semaphores[unlock_sem],LONG_MAX);
              detail::win32::release_semaphore(semaphores[exclusive_sem],LONG_MAX);
              boost::throw_exception(thread_resource_error());
            }

While this is not too elegant it solves the issue. A RAI handle would be also appreciated.

[viboes]

Committed in trunk At revision: [75806]

[viboes]

Let close the ticket when merged to release

[viboes]

Committed in release at [76291]