[M3commit] CVS Update: cm3

[Antony Hosking]

CVSROOT:	/usr/cvs
Changes by:	hosking at birch.	09/09/08 07:54:58

Modified files:
	cm3/m3-libs/m3core/src/convert/: CConvert.m3 
	cm3/m3-libs/m3core/src/runtime/common/: RTAllocator.m3 
	                                        RTCollector.m3 
	                                        RTCollectorSRC.i3 
	                                        RTHeapInfo.m3 
	                                        RTHeapRep.i3 
	                                        RTHeapRep.m3 
	                                        RTHeapStats.m3 
	                                        RTLinker.m3 RTOS.i3 
	cm3/m3-libs/m3core/src/runtime/ex_frame/: RTExFrame.m3 
	cm3/m3-libs/m3core/src/runtime/ex_stack/: RTExStack.m3 
	cm3/m3-libs/m3core/src/thread/POSIX/: ThreadF.i3 ThreadPosix.m3 
	cm3/m3-libs/m3core/src/thread/PTHREAD/: ThreadF.i3 
	                                        ThreadPThread.m3 
	cm3/m3-libs/m3core/src/thread/WIN32/: ThreadF.i3 ThreadWin32.m3 

Log message:
	Tidy up use of thread.inCritical to only occur in allocation sequences and in
	thread stoppage.  This simplifies reasoning.  Refactored use of heap lock
	in the process.  This may be better implemented on PTHREAD targets using a
	recursive pthread mutex instead of one we roll ourselves from a non-recursive
	mutex.
	
	Still witnessing random hangs in Juno and mentor on I386_DARWIN.
	Strange, I thought this was working previously.
	I wonder if there is some sort of race in the GUI code somewhere?