No - the critsec_count is internal to the PAL and is maintained automatically for constructs like critical sections. Barry
-----Original Message----- From: Discussion of the Rotor Shared Source CLI implementation [mailto:[EMAIL PROTECTED] On Behalf Of Archana Sent: Thursday, July 03, 2003 1:03 AM To: [EMAIL PROTECTED] Subject: Re: [DOTNET-ROTOR] Using posix calls in rotor code > > Be very careful adding new locks into the PAL - if you do, you'll need > to update the critsec_count in order to avoid PAL-internal deadlocks. if i add additional critical sections/mutexes in the /vm code, do i need to update this critsec_count? > > Barry > This posting is provided "AS IS" with no warranties, and confers no > rights. > Regards, archana
