Crash with invokeDynamic on MethodMissing attempt
Charles Oliver Nutter
charles.nutter at sun.com
Tue May 19 20:16:12 PDT 2009
Check in netbeans-ant.xml, there should be one or more debug targets in
there and instructions on how to modify the JRuby command line. I
*think* they still work, but I don't use NB debugging much.
Note that it's passing the arguments directly to 'java' and
org.jruby.Main, so JVM args would be -server instead of --server,
-XX:+EnableInvokeDynamic instead of -J-XX:... and so on. -e or a script
name as arguments to Main will still work fine.
John Rose wrote:
> I've reproduced your crash from the command line; thanks for the clean
> The crash is for:
> def foo(a); end; a = 1; while a < 1_000_000; foo(a); a += 1; end
> There is a basic nbproject in the jruby repo, but no debug or run
> Is there a secret combination to getting a debugger session on the
> equivalent of this command line?
> bin/jruby --server -J-XX:+EnableInvokeDynamic -J-
> Djruby.compile.invokedynamic=true script.rb
> -- John
> On May 18, 2009, at 4:29 PM, Charles Oliver Nutter wrote:
>> Here you go! The details of getting it to run under mlvm are up to
>> but jruby accepts options like -J-XX:+EnableInvokeDynamic, etc.
>> git clone git://kenai.com/jruby~main jruby
>> cd jruby
>> git co -b invokedynamic origin/invokedynamic
>> ant clean jar (with MLVM as JAVA_HOME)
>> bin/jruby <important flags here> -e "code here"
>> bin/jruby <important flags here> script.rb
>> Where important flags are:
>> --server (-server flag to JVM, if you want it)
>> Not a whole lot of logging/debugging in place at the moment, but if
>> also pass --bytecode to JRuby it will dump out the bytecode for the
>> target script rather than run it. If it's wiring up right you'll see
>> INVOKEDYNAMIC in there.
> mlvm-dev mailing list
> mlvm-dev at openjdk.java.net
More information about the mlvm-dev