Peter Brant wrote:
Your suggestion in JRUBY-1475 (add a flag at startup) makes sense to me.
How feasible would it be to add debugging information as part of a
bytecode transformation (either as an additional visitor when it's
being created or transforming it in the ClassLoader after the fact)?
Flipping a switch in the compiler to emit tracing would be pretty
trivial to do. Once we identify everywhere that needs the trace calls,
it's maybe a day job.
Transforming the bytecode at runtime is an interesting proposition
though. In order to support debugging of code that's pre-compiled to
classes, we'd have to have something like that...or emit tracing into
the generated classes by default. But I'm starting to wonder if AOT
compiled execution is going to be a use case we really need to support
for debugging anyway. Hmmm.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
