On Tue, Jul 7, 2009 at 4:16 AM, Christian Thalinger<[email protected]> wrote: > That looks good too. Is this the command you executed (I think I read > it correctly from the error): > > $ jruby -Djruby.compile.invokedynamic=true -XX:+EnableInvokeDynamic -d > -e puts 1 > > Because that works for me. Well, it does not print anything, as I > supposed, but it does not crash.
You're missing the -J in front of those JVM options, but yes, it crashes for me: ➔ jruby -J-Djruby.compile.invokedynamic=true -J-XX:+EnableInvokeDynamic -e puts 1 # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x011a4d7a, pid=39691, tid=2954375168 # # JRE version: 7.0 # Java VM: OpenJDK Client VM (16.0-b03 mixed mode bsd-x86 ) # Problematic frame: # V [libjvm.dylib+0x1a4d7a] # # An error report file with more information is saved as: # /Users/headius/projects/jruby/hs_err_pid39691.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Abort trap It *also* crashes without invokedynamic, as in "jruby -e puts 1" or "jruby -v". Maybe my bsd-port is behind? I'll try updating it and see. - Charlie _______________________________________________ mlvm-dev mailing list [email protected] http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
