Re: CACAO 0.95 relased

On Tue, 2006-02-14 at 18:10 +0100, Robert Schuster wrote: > Hi Twisti, > Great stuff about the new release. However my Eclipse now fails at startup > with > this ugly message: > > The error was 'BadAlloc (insufficient resources for operation)'. > (Details: serial 6303 error_code 11 request_code

Re: CACAO 0.95 relased

Hi Twisti, Great stuff about the new release. However my Eclipse now fails at startup with this ugly message: The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 6303 error_code 11 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported

Re: CACAO 0.95 relased

Christian Thalinger writes: > On Tue, Feb 14, 2006 at 11:24:18AM +, Andrew Haley wrote: > > Christian Thalinger writes: > > > * i386 bugfix: Set FPU to 64-bit on VM startup (fixes Debian bug > > > #350729) > > > > Interesting. Do libcalls still work after you've done this? Is i

Re: CACAO 0.95 relased

On Tue, Feb 14, 2006 at 11:24:18AM +, Andrew Haley wrote: > Christian Thalinger writes: > > * i386 bugfix: Set FPU to 64-bit on VM startup (fixes Debian bug > > #350729) > > Interesting. Do libcalls still work after you've done this? Is it > even legal to make library calls with the

Re: CACAO 0.95 relased

Christian Thalinger writes: > * i386 bugfix: Set FPU to 64-bit on VM startup (fixes Debian bug > #350729) Interesting. Do libcalls still work after you've done this? Is it even legal to make library calls with the FPU in a nonstandard mode? I've always been a little reluctant to make gc

CACAO 0.95 relased

CACAO 0.95 released. This is mainly a bugfix release. Here is a short list of the most important changes: * Dead-lock bugfix. This should fix the random dead-locks seen in Eclipse or other applications. * Search for suitable jar program during configure, can be specified via JAR env