We have run into the following problem when working on getting a Condor-G 
running on Win32 using the Globus 2.x Win32 libraries:

the problem we saw w/ the globus win32 alpha libraries was if you created a 
mutex X with globus_mutex_lock() in thread A and released it
with globus_mutex_unlock() in thread B, nobody could grab mutex X again (in 
either thread A or thread B) --- it was as if the code never "noticed" that 
mutex X was every released.

i admit grabbing a lock in thread A and releasing it in thread B is a little 
uncommon.  but this code *does work* on Unix.  question: anywhere in the globus 
toolkit proper are locks created in one thread and released in another?  if 
not, then we could easily work around this issue by using a Win32 critical 
section in our code instead of a globus_mutex_lock().  but if some parts of the 
globus toolkit also use locks this way, things will be broken under the 
covers...

thanks in advance for your feedback...

-Todd Tannenbaum, Condor Project, Univ of Wisconsin