FYI, this is now the primary issue keeping me from continuing to wire up invokedynamic paths in JRuby. Have not yet reduced a test case for it.
- Charlie On Sat, May 14, 2011 at 11:26 AM, Charles Oliver Nutter <head...@headius.com> wrote: > Current build as of an hour ago. Made some changes to bind more > handles straight through, and got this: > > ~/projects/jruby ➔ jruby -d -X+C --server -e "class Foo; attr_accessor > :bar; end; f = Foo.new; loop do; f.bar; end" > argCount: 4 > inbound: > (ThreadContext,IRubyObject,IRubyObject,String,IRubyObject[],Block)IRubyObject > permute: [2, 0, 4] > before permute: > attr_accessor(IRubyObject,ThreadContext,IRubyObject[])IRubyObject > # > # A fatal error has been detected by the Java Runtime Environment: > # > # Internal Error (methodHandleWalk.cpp:1092), pid=24359, tid=2962804736 > # Error: ShouldNotReachHere() > # > # JRE version: 7.0 > # Java VM: OpenJDK Server VM (21.0-b09 mixed mode bsd-x86 ) > # Failed to write core dump. Core dumps have been disabled. To enable > core dumping, try "ulimit -c unlimited" before starting Java again > # > # An error report file with more information is saved as: > # /Users/headius/projects/jruby/hs_err_pid24359.log > [thread -1332695040 also had an error] > # > # If you would like to submit a bug report, please visit: > # http://bugreport.sun.com/bugreport/crash.jsp > # > Abort trap > > Apparently I did reach "Here" :) > > I'm going to push my changes so others can try it out, and try to > narrow down where it's happening. > > Log is attached. > > - Charlie > _______________________________________________ mlvm-dev mailing list mlvm-dev@openjdk.java.net http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
