dcsimg
Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Home » Tip Bank » C++
Language: C++
Expertise: Intermediate
Sep 10, 2002

WEBINAR:

On-Demand

Building the Right Environment to Support AI, Machine Learning and Deep Learning


Every Call to "EnterCriticalSection" Needs a Matching "LeaveCriticalSetcion"


Threads can hang indefinitely if one thread is Entered in a critical section but returned without Leaving it. There is a simple solution to make sure that this doesn't happen. Wrap the CriticalSection in a class and instantiate it on the stack like this.
 
class CSafeCriticalSection
{
private:
	// the pointer to the critical section
	LPCRITICAL_SECTION m_pCS;
public:
	CSafeCriticalSection(LPCRITICAL_SECTION pCS) : m_pCS(pCS)
	{
		if(m_pCS)
			EnterCriticalSection(m_pCS);
	}
	~CSafeCriticalSection()
	{
		if(m_pCS)
			LeaveCriticalSection(m_pCS);
	}
};

Then, in any function that uses your critical section (assume you have a critical section called m_CS):
 
HRESULT MyClass::Foo()
{
   CSafeCriticalSection SafeCS(&m_CS);
   // DO YOUR WORK HERE

   // you can return anywhere
   // without worrying about the critical section
   return hr;
}
Vinayak Raghuvamshi
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date