🚀 go-pugleaf

Hello,

I used to have an application with the following functions for thread 
sync'in.

void inline __fastcall lockCriticalSection(TCriticalSection 
*criticalSection)
{
  criticalSection->Acquire();
};

void inline __fastcall releaseCriticalSection(TCriticalSection 
*criticalSection)
{
  criticalSection->Release();
};


To detect a deadlock, I implemented the below:

void inline __fastcall lockCriticalSection(TCriticalSection 
*criticalSection)
{
  HANDLE hMutex;

  // Create a mutex with no initial owner.

  hMutex = CreateMutex(
   NULL,                       // no security attributes
   true,                      // initially owned
   String((int)(void*)criticalSection).c_str());  // name of mutex

  DWORD dwWaitResult;

  // Request ownership of mutex.

  if(hMutex)
  {
   dwWaitResult = WaitForSingleObject(
   hMutex,   // handle to mutex
   5000L);   // five-second time-out interval

   switch(dwWaitResult)
   {
    // Cannot get mutex ownership due to time-out.
    case WAIT_TIMEOUT:
     throw Exception("BUG FOUND, CHECK CALL STACK!");

    // Got ownership of the abandoned mutex object.
    case WAIT_ABANDONED:
     break;
   }
  }

  criticalSection->Acquire();
};

void inline __fastcall releaseCriticalSection(TCriticalSection 
*criticalSection)
{
  criticalSection->Release();

  HANDLE hMutex;

  // Create a mutex with no initial owner.

  hMutex = OpenMutex(
    MUTEX_ALL_ACCESS,
    false,
    String((int)(void*)criticalSection).c_str()
  );  // name of mutex

  if(hMutex)
  {
   DWORD dwWaitResult;

   // Request ownership of mutex.

   dwWaitResult = WaitForSingleObject(
    hMutex,   // handle to mutex
    5000L);   // five-second time-out interval

   switch(dwWaitResult)
   {
    // The thread got mutex ownership.
    case WAIT_OBJECT_0:
     // Release ownership of the mutex object.
     if(!ReleaseMutex(hMutex))
     {
      // Deal with error.
     }

     break;

    // Cannot get mutex ownership due to time-out.
    case WAIT_TIMEOUT:
     break;

    // Got ownership of the abandoned mutex object.
    case WAIT_ABANDONED:
     break;
   }
  }
};

which does not work for no obvious reason. It simply raises the exception 
when there is no reason! The Critical section variable is -1, 0 at that 
time!

Please help!

Best Regards,

SZ