ASSERTs are killing my multithreaded MFC app!

[werp]

I am using CCriticalSection and CSingleLock in an MFC app. I have created an object and pass into it a CCriticalSection from the main app. Then I make a thread. The thread constantly writes data to some structures. The main app then reads those same structures hoping that the CCriticalSection and CSingleLock will block the read until the write thread has lost access to the structures.

What happens is ASSERT! I keep finding that my CSingleLock.m_bAcquired == true. When this happens the ASSERT pounds the desktop.

I don't understand how m_bAcquired becomes true.

I create the locking mechanism with a wrapper class. It is included below.
Please note that my destructor is doing an Unlock.
Please note that my constructor accepts a CSingleLock instantiated with the CCriticalSection created in the main thread.
The CSingleLock is static in the class that consumes the code below.

FYI: I have read the following thread and it doesn't appear to be relevant:
http://www.thescripts.com/forum/thread283101.html

[code]
class CQCriticalSection
{
public:

CQCriticalSection(CSingleLock* pcslLock);

virtual ~CQCriticalSection();

private:

CSingleLock* m_pcslLock;

};

CQCriticalSection::CQCriticalSection(CSingleLock* pcslLock)
{

_ASSERT(pcslLock != static_cast<const CSingleLock*>(0));

m_pcslLock = pcslLock;

m_pcslLock->Lock();

};

CQCriticalSection::~CQCriticalSection()

{if (m_pcslLock != static_cast<CSingleLock*>(0))

{

m_pcslLock->Unlock();

}

}

[werp]

My fault here was accepting a CSingleLock as a parameter into my constructor. I should have made a CSingleLock local by creating it the constructor and instead have passed into the constructor a CCriticalSection.

Doing this solved my issues.