John Rose wrote: > That reminds me of a bug we fixed in the mlvm patches during JavaOne; > it was a heap stomping problem. I don't think there was a workaround. > > I think you have two options with this problem: > - wait for the mlvm changes to percolate into JDK7 and the JDK7 > standard builds > - obtain or build a version of the JVM from the mlvm patches (or have > you done this?)
I get a similar assert when using javap: $ javap -c test # # A fatal error has been detected by the Java Runtime Environment: # # Internal Error (frame.cpp:1209), pid=59254, tid=2953654272 # Error: ShouldNotReachHere() VM_Operation (0xb00502ec): GenCollectForAllocation, mode: safepoint, requested by thread 0x00801400 Are you sure that bug is fixed? -- Christian _______________________________________________ mlvm-dev mailing list [email protected] http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
