Actually nearly all critical sections in Wine are initialized
statically. This improves performance, and avoids having lots of
"init" functions called all over the place. I'm not convinced it's
worth changing that just to be able to build a list of sections.
It also lets you name them more easily w
Robert Reif <[EMAIL PROTECTED]> writes:
> Is there a good reason to statically initialize ntdll locks or
> can they be initialized like normal locks?
Actually nearly all critical sections in Wine are initialized
statically. This improves performance, and avoids having lots of
"init" functions cal
I have been running into deadlock problems in the direct sound
dll and have been playing with the debug part of critical
sections. I added a lock name to Spare[1] to give the critical
sections names that will show up in the error messages just
like wine's ntdll does. After looking at the ntdll co
