As far as 1352, the relevant portion of the stack trace is:
java.lang.NullPointerException
at org.jruby.javasupport.JavaClass$MethodCallback.createJavaMethods(JavaClass.java:306)
at org.jruby.javasupport.JavaClass$StaticMethodInvoker.execute(JavaClass.java:356)
at org.jruby.internal.runtime.methods.SimpleCallbackMethod.call(SimpleCallbackMethod.java:70)
at org.jruby.runtime.CallSite$InlineCachingCallSite.call(CallSite.java:144)
at org.jruby.runtime.CallSite$ArgumentBoxingCallSite.call(CallSite.java:103)
at org.jruby.evaluator.ASTInterpreter.callNode(ASTInterpreter.java:652)
MenTaLguY - 24/Dec/07 03:49 PM As far as 1352, the relevant portion of the stack trace is:
java.lang.NullPointerException
at org.jruby.javasupport.JavaClass$MethodCallback.createJavaMethods(JavaClass.java:306)
at org.jruby.javasupport.JavaClass$StaticMethodInvoker.execute(JavaClass.java:356)
at org.jruby.internal.runtime.methods.SimpleCallbackMethod.call(SimpleCallbackMethod.java:70)
at org.jruby.runtime.CallSite$InlineCachingCallSite.call(CallSite.java:144)
at org.jruby.runtime.CallSite$ArgumentBoxingCallSite.call(CallSite.java:103)
at org.jruby.evaluator.ASTInterpreter.callNode(ASTInterpreter.java:652)
MenTaLguY - 24/Dec/07 05:56 PM r5351 should fix this as far as adding minimally needed synchronization on the MethodCallback's monitor. We need to do some code cleanup though.
java.lang.NullPointerException
at org.jruby.javasupport.JavaClass$MethodCallback.createJavaMethods(JavaClass.java:306)
at org.jruby.javasupport.JavaClass$StaticMethodInvoker.execute(JavaClass.java:356)
at org.jruby.internal.runtime.methods.SimpleCallbackMethod.call(SimpleCallbackMethod.java:70)
at org.jruby.runtime.CallSite$InlineCachingCallSite.call(CallSite.java:144)
at org.jruby.runtime.CallSite$ArgumentBoxingCallSite.call(CallSite.java:103)
at org.jruby.evaluator.ASTInterpreter.callNode(ASTInterpreter.java:652)