1

For example, is this valid?

CRITICAL_SECTION cs_A;
CRITICAL_SECTION cs_b;

::InitializeCriticalSection( &cs_A );
::InitializeCriticalSection( &cs_B );

::EnterCriticalSection( &cs_A );      // First level

/* do some stuff with A */

::EnterCriticalSection( &cs_B );        // Second level

/* do some stuff with A and B */

::LeaveCriticalSection( &cs_B );        // Second level

/* do some stuff with A */

::LeaveCriticalSection( &cs_A );      // First level

::DeleteCriticalSection( &cs_A );
::DeleteCriticalSection( &cs_B );

I would like to protect two very section of code with two critical sections. Can I do this?

Possible Duplicates: Is it valid to nest a critical section?

Community
  • 1
  • 1
Control
  • 49
  • 1
  • 8

2 Answers2

1

Whenever you have multiple locks and more than one lock may be held at one point in time, then you must make sure that the locks are always acquired in the same order. Failure to observe this can lead to deadlock.

This is a widely known and widely discussed rule. For instance, Use Lock Hierarchies to Avoid Deadlock.

David Heffernan
  • 601,492
  • 42
  • 1,072
  • 1,490
0

I think your question is different form the one you mention, since you have two distinct critical sections.

Anyway you can nest them but you must take the care of enter/acquire them always in the same order, otherwise you risk a deadlock.

marom
  • 5,064
  • 10
  • 14