Now you're getting deep into the bowels of my threading code. criticalizeOrDieIfKilled waits on a lock when critical= is set to true somewhere in the system. If the thread is killed, it will die once it wakes up. Both situations are handled here, and the method is called fairly frequently.
If you'r
Hi.
The time has come to rewrite Zlib FAST, so it'll actually be usable. This
should not cause much of a problem and would probably speed things up a
magnitude or something like that.
I happened upon a strange error inside remote_installer.rb where RubyGems
fetches the source-index remotely:
ni <[EMAIL PROTECTED]>
Date: Wednesday, March 22, 2006 6:13 pm
Subject: [Jruby-devel] Zlib and RubyGems.
To: [email protected]
> Hi.
>
> It's going forward. I'll soon send in patches for the error with
> IO-objects. Wrappers seem to solve that problem, but n
Hi.
It's going forward. I'll soon send in patches for the error with
IO-objects. Wrappers seem to solve that problem, but now something else
seems very strange. This error comes from the bowels of JRuby, and I
can't get a fix on what in the post-install-script that triggers it.
This is the output:
