Martin Krauskopf wrote:
jruby.jit.enabled=false: thanks for the tip Charles, this might be used
by the GUI frontends utilizing stf (CCing possibly interested folks)
But still the problem for JRuby itself and people trying to use the
debugger in a classic way, requiring debug.rb. Might be you should
adjust behavior of the interpreter somehow when debug.rb is required if
possible or at least put a warning message into debug.rb?
Well I suppose we have a few options. I suggested this initially because
I don't want to pollute the compiled code with calls to check for
tracing every line, call, etc. It's miserable to do all those callbacks
all the time, and would surely slow down compiled code all the time, not
just when debugging.
I just committed an additional change that prevents the "main" script
from compiling if a trace function is set; since -rdebug.rb sets a trace
function before execution starts, this will effectively disable
compilation throughout the runtime, and so people expecing debug.rb to
work right will be satisfied.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
