JRuby

[RubySpec] New backtrace logic does not generate (strange) caller() backtrace for eval'ed cases

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Incomplete
  • Affects Version/s: JRuby 1.6RC1
  • Fix Version/s: None
  • Component/s: Core Classes/Modules, RubySpec
  • Labels:
    None
  • Number of attachments :
    0

Description

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.

Activity

People

  • Assignee:
    Charles Oliver Nutter
    Reporter:
    Charles Oliver Nutter
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: