Posted on 1998-11-18
I have some threads, which can call a function from a single
object, let's say CBoss.
When I declare a CCriticalSection class in the header of
CBoos ( CCriticalSection m_readSection;)
and I try to access the function of this class from a thread-class in the next way:
CSingleLock m_readSection(&m_pDoc->m_readSection, FALSE);
the thread stops on the second Lock (i.e. when I try to lock the second time the CriticalSection, the thread begin to wait, even if the CSingleLock object - m_readSection is
not locked- I have checked this). There is only one thread,
so doesn't exist another thread to lock this critical section.
When I use in the CBoss header
static CRITICAL_SECTION m_readSect;
and I try to access the function of this class from a thread class in the next way:
What's wrong with the use of MFC classes?