Clean up and formalize markers and structure for Java stacktrace-driven
backtrace generation
--------------------------------------------------------------------------------------------
Key: JRUBY-5426
URL: http://jira.codehaus.org/browse/JRUBY-5426
Project: JRuby
Issue Type: Improvement
Components: Compiler
Affects Versions: JRuby 1.6RC1
Reporter: Charles Oliver Nutter
Fix For: JRuby 1.6.1
Currently there are around five different markers used to indicate that a Java
stacktrace frame is from compiled Ruby code. Checking for each of these markers
in turn is messy and likely slows the generation of backtraces.
In addition, the structure of those mangled names is not completely standard,
differing subtly between jitted and AOT-compiled code.
For 1.6.1, I want to clean this up and simplify the backtrace generation logic.
In addition, I'd like to benchmark backtrace generation and do as much as
possible to cheapen it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
