Bluecove is willing to use its native lib on OS X 10.5 with a 64 bit JVM

What steps will reproduce the problem?

1. Build the mac os x native library with 64 bit support.
2. Attempt to use bluecove on 10.5 with a 64 bit JVM.
3. Machine will stop responding to input. Sometimes it clears on it's own
in 20 seconds, otherwise putting it to sleep seems to resolve the problem.

What is the expected output? What do you see instead?

I'd be very interested in turning on 64 bit bluecove Mac support, since it
works on Snow Leopard. However we can't flip that switch until we protect
Leopard users from this lockup.

What BlueCove version are you using (include build number for SNAPSHOT)? On
what operating system and jvm? Is this 64-bit or 32-bit OS and jvm?

The problem is on OS X 10.5 with a 64 bit jvm.

Please provide any additional information below.
Please use "Attach a file" when uploading stack traces or other big files!

I've attached a patch that prevents this combination of OS and JVM from
attempting to use the native library. With the patch in, I think we could
safely close bug 35 (with an unhappy resolution, alas).

Apple has made no indications that they intend to fix the problems with 64
bit IOKit on Leopard, and with the release Snow Leopard such a fix looks
increasingly unlikely.

With this patch in svn and Leopard users protected, we could enable 64 bit
compilation of the mac native lib, thus bringing bluecove to 64 bit jvms on
Snow Leopard.

Original issue reported on code.google.com by christop...@gmail.com on 9 Feb 2010 at 9:49

Attachments:

bluecove-leopard-64-bit-jre.diff

INeedCaffeine / bluecove

Bluecove is willing to use its native lib on OS X 10.5 with a 64 bit JVM #100