Am 07.04.2005 um 10:38 schrieb Zoran Vasiljevic:
the leak is gone. Now I have to rewind the stack and try to
figure out what did the author(s) *really* wanted to do.
Seems that somebody was cleaning up some state but cleaned
up much to much...
I have opened Tcl Bug #1178445 to track this issue.
I have also corrected it in the core-8-4-branch in SF.
I will await (see below) and if all is well, I will
apply this to the head branch as well.
BTW, the problem was introduced by an attempt to make a clean
Tcl library unload when somebody calls Tcl_Finalize().
Unfortunately, it broke the glass on the other place...
Well, as Jeff said once:
"You cannot make an omellette without breaking some eggs"
Jeff, thanks for the saying :-) and please do me a favour.
Can you check the windows build after updating your core-8-4-branch?
I have no access to Windows machine and have made all changes blindly.
I was careful, but you never now unless you test it. Just compile,
load threading extension and do:
time {thread::join [thread::create -joinable ""]} 1000
It should not core nor leak any more. The Unix part is checked
already by myself and it works properly now.
Zoran
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
