🚀 go-pugleaf

SubZero wrote:

>Ok. The original functions will be used with only TCriticalSection (single
>line). The reason for all the code is that it is needed for detecting the
>deadlock. I want to raise an exception so that MadExcept can show the stack!
>Hope you understand now. Sorry for the confusion.
>
>I cannot create the mutexes at startup because there are countless
>criticalsections. It must work within these two functions with named
>mutexes.

You still need to call CreateMutex with false, not true.
You still need to CloseHandle for every CreateMutex and OpenMutex.

Suggested outline:
whatever lockCritSec( whatever)
{
	HANDLE	 M;
	BOOL	opened = true;
	M = OpenMutex( flag, false, name);
	if( M == NULL )
	{	// create only if needed (first time)
		opened = false;
		M = CreateMutex( flag, false, name );	
		if( M == NULL )
		{handle failure and return};
	};
	switch( WaitForSingleObject( M, 5000 ) )
	{case WAIT_TIMEOUT:
		/*whatever */
	default:
		break;
	};
	if( opened )
		CloseHandle( M );
}
whatever releaseCritSec( whatever)
{
	HANDLE	 M;
	M = OpenMutex( flag, false, name);
	if( M == NULL )
	{handle failure and return};

	// note that there is no wait() nor aquire at this point,
	// we should already own the mutex
	// and we only want to release it.

	ReleaseMutex( M );
	CloseHandle( M );
}

This way, at least you only have one dangling handle for each CritSec.