New backtrace logic does not generate (strange) caller() backtrace for eval'ed
cases
------------------------------------------------------------------------------------
Key: JRUBY-5176
URL: http://jira.codehaus.org/browse/JRUBY-5176
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Affects Versions: JRuby 1.6
Reporter: Charles Oliver Nutter
In MRI 1.8 and JRuby prior to the new backtrace logic, caller(0) from within an
eval shows as its 2nd element (index 1) the *caller's* caller. There are
RubySpecs to this effect, but the behavior is so peculiar the new backtrace
logic does not obey it. I am tagging those specs and will likely add a
deviates_on :jruby section with our behavior.
--
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
