Interesting - was this ever entered as a bug to be fixed at all? Or did it just get lost in the mailing list?
Mark On Tue, Jun 10, 2008 at 12:12 AM, Kevin Conaway <[EMAIL PROTECTED]> wrote: > Hi Mark, > > I had the same problem as you. I tweaked some lines of code in that class > and recompiled and the issue went away. > > It feels like a bug in the JVM because the error is happening when Hotspot > decides to recompile the class. I never did figure out what was causing > it. > > I had posted to [EMAIL PROTECTED] back in April: > > http://restlet.tigris.org/servlets/ReadMsg?list=code&msgNo=139 > > Kevin > > > On Wed, Jun 4, 2008 at 12:37 AM, Rob Heittman <[EMAIL PROTECTED]> > wrote: > >> That's a new one on me, but Hardy has been the locus of a bunch of new JVM >> crash issues, mainly with Athlon processors. Also there have been some >> similar issues with 64-bit under Red Hat and Fedora. >> This is the Sun JVM I get installing sun-java6-jdk from multiverse, and I >> don't get JVM crashes on P4, Centrino, or Core Duo. >> >> java version "1.6.0_06" >> Java(TM) SE Runtime Environment (build 1.6.0_06-b02) >> Java HotSpot(TM) Client VM (build 10.0-b22, mixed mode, sharing) >> >> Where did you get yours from? Direct Sun download? Hardy tries very hard >> to use OpenJDK, which also doesn't crash for me on P4, Centrino, or Core >> Duo. >> >> - Rob >> >> > -- "It is easier to optimize correct code than to correct optimized code." -- Bill Harlan
