howdy,
since there was talk about planning 1.2: any plans on actually using the
JVMs debugger instead of doing the trace-based debugging?
As far as I understand, IronRuby generates debugging information in the
generated IL (or PDB or whatever it's called), which should mean running
stuff under the debugger shouldn't have much of a overhead (as compared
to trace-based debugging which slows down execution considerably).
I understand that there are issues, like the fact that only a certain
part of the code is actually turned into bytecode (eg. AST interpreted
code vs JITed/AOTed code) but I was wondering if someone has considered
changing the debugging cost from a cost per executed line to a cost per
invoked breakpoint.
Yes I'm aware of jruby-debug and this
http://www.sapphiresteel.com/JRuby-Debugging-In-Visual-Studio - but
these are still trace-based.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
