Changes by: Aleksey Nogin (nogin at metaprl.org)
Date: 2007-07-19 12:19:39 -0700 (Thu, 19 Jul 2007)
Revision: 11356
Log message:

      Trying to debug the deadlocks I am seeing on Windows when -p is enabled. What I am seeing is that the worker threads are being created, but they never start (even the child part of the Lm_thread.create_thread is never executed). I have no idea how the -p causes this...
     
     In this commit I:
     - Added a lot of thread-related debugging code
     - Made the -debug-thread command-line option also activate Lm_thread.debug_lock and Lm_thread_code.debug_mutex (the latter variable is new).
     - Changed the Lm_thread_core_null so that Lm_thread.Mutex.try_lock would return a value consisntent with the real thread implementation.

Changes  Path
+13 -9 libmojave/stdlib/lm_thread.ml
+8 -7 libmojave/stdlib/lm_thread.mli
+11 -7 libmojave/stdlib/lm_thread_core.mli
+31 -19 libmojave/stdlib/lm_thread_core_null.ml
+113 -8 libmojave/stdlib/lm_thread_core_system.ml
+15 -6 libmojave/stdlib/lm_thread_pool_system.ml
+3 -5 libmojave/stdlib/lm_thread_sig.ml
+1 -1 libmojave/util/lm_hash.ml
+1 -1 libmojave/util/lm_symbol.ml
+1 -1 libmojave/util/lm_symbol_hash.ml
+2 -0 omake-branches/0.9.8.x/src/main/omake_main.ml