[ros-dev] Re: [ros-svn] [arty] 13483: Patch to fix
NtCreateSempahore, in the case where the initial lookup
ayerkes at speakeasy.net
Thu Feb 10 11:09:29 CET 2005
On Thu, 10 Feb 2005 10:18:05 +0100
Thomas Weidenmueller <w3seek at reactos.com> wrote:
> The previous version I wrote just had one small bug, it checked if
> ObCreateObject failed to continue initialization and handle creation
> instead of checking if it succeeded. I'm going to revert this version of
> NtCreateSemaphore as it introduces even more bugs and adds behavior
> neither documented nor reproducable. I guess in case an application
> failed due to this function it was because of the fact that the function
> succeeded and didn't return a handle to a semaphore object even though
> one was created.
Well it is a bit unkind to make a new semaphore and not return the handle
to it. Thanks for fixing it the right way.
Here's a simple experiment. Stand on a train track between two locomotives
which are pushing on you with equal force in opposite directions. You will
exhibit no net motion. None the less, you may soon begin to notice that
something important is happening.
-- Robert Stirniman
More information about the Ros-dev