C / C++ / MFC

ForNow wrote:

go to disassembly mode

ForNow wrote:

It's the handle I guess the next step is to go to disassembly mode and see

!handle	displays information about a handle or handles that one or all processes in the target system own.

0:000> !handle c0dedbad f
Handle 38
 Type Mutant
 Attributes 0
 GrantedAccess 0x1f0001:
 Delete,ReadControl,WriteDac,WriteOwner,Synch
 QueryState
 HandleCount 1
 PointerCount 96605
 Name <none>
 Object Specific Information
 Mutex is Owned
 Mutant Owner 11bc.1418

//Windows 8.1 and below:
BOOL IsValidHandle(HANDLE h)
{
	DWORD dwFlags = 0;
	return GetHandleInformation(h,&dwFlags);
}

//Windows 10 and above:
BOOL IsValidHandle(HANDLE h)
{
	return CompareObjectHandles(h,h);
}

if (IsValidHandle(h))
{
	DWORD dwResult = ::WaitForSingleObject(h, INFINITE);
	DWORD dwError = GetLastError();
}

Two or more processes can call CreateMutex to create the same named mutex. The first process actually creates the mutex, and subsequent processes open a handle to the existing mutex. This enables multiple processes to get handles of the same mutex, while relieving the user of the responsibility of ensuring that the creating process is started first. When using this technique, you should set the bInitialOwner flag to FALSE; otherwise, it can be difficult to be certain which process has initial ownership.

The creating thread can use the bInitialOwner flag to request immediate ownership of the mutex. Otherwise, a thread must use one of the wait functions to request ownership. When the mutex's state is signaled, one waiting thread is granted ownership, the mutex's state changes to nonsignaled, and the wait function returns. Only one thread can own a mutex at any given time. The owning thread uses the ReleaseMutex function to release its ownership.

If lpName matches the name of an existing event, semaphore, waitable timer, job, or file-mapping object, the function fails and the GetLastError function returns ERROR_INVALID_HANDLE. This occurs because these objects share the same namespace.

Member 12335695 wrote:

Please let me know how we can resolve it.

Member 12335695 wrote:

hWaits is an array of 32 handles

Debug Assertion Failed!

Program: C:\Windows\system32\mfc120ud.dll
File: f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\barstat.cpp
Line: 99

For information on how your program can cause an assertion
failure, see the Visual C++ documentation on asserts.

(Press Retry to debug the application)
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\winfrm.cpp(1628) : AppMsg - Warning: no message line prompt for ID 0xE001.

Member 12335695 wrote:

Program: C:\Windows\system32\mfc120ud.dll
File: f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\barstat.cpp
Line: 99
 
For information on how your program can cause an assertion
failure, see the Visual C++ documentation on asserts.
 
(Press Retry to debug the application)
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\winfrm.cpp(1628) : AppMsg - Warning: no message line prompt for ID 0xE001.

STRINGTABLE
BEGIN
    ATL_IDS_IDLEMESSAGE     "Ready"
END

void main()
{
    HPCORE hPCore = CreateNewPCore();
    while(true){
       PCoreDoSomething(hPCore);	
     }
     DestroyPCore(hPCore);
}

Handle Index = (Handle - &PCoreArray[0])/sizeof(Pointer).

typedef size_t HPCORE;