Folks,
	Enclosed is a fix to this serious bug.  If your system has 
update 4436, and if you have the preference set to log errors to a 
file, you will need this fix.  (It will come out later as an update.)

--Ted.

At 11:14 AM +0000 12/5/01, Henrik Gedenryd wrote:
>Now I can reproduce this problem (warning: this will cause Squeak to
>eventually hang):

      [Set the preference to log errors to a file.]

>In something recent, open a file list, look at a text
>file, and make a small change to it. Now accept it (cmd-s), but choose
>cancel when asked whether to overwrite or not.
>
>You are now in trouble ;-) From this point, to quit Squeak you will have to
>terminate the VM from the outside.
>
>Press cmd-. to get a walkback, the system has locked when trying to write
>into SqueakDebug.log -- which also means that I don't have a stack trace to
>provide here. It is however stuck in Semaphore>> critical:ifError: due to a
>lock on some WeakRegistry object it is trying to print into the log file.
>[snip]
>Henrik

-- 
Ted Kaehler         http://www.squeakland.org/~ted/
When we were young, we were told that "everybody else is doing it" 
was a really stupid reason to do something.  Now it's the standard 
reason for picking a particular software package. -- Barry Gehm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Urgent-errorLog-tk.cs
Type: application/mac-binhex40
Size: 2451 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20011205/20453ab2/Urgent-errorLog-tk.hqx