Hello again!

I'm using Thread#backtrace_locations and noticed several differences between MRI and JRuby.

I'll report them separately because they may have different fixes, but feel free to mark any as duplicate if it makes sense to do so.

Environment

• JRuby: jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 Java HotSpot(TM) 64-Bit Server VM 25.171-b11 on 1.8.0_171-b11 +jit [linux-x86_64]
• Kernel: Linux u186024434db159d25c92 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
• Distro: Ubuntu 16.04.4 LTS

Expected Behavior

On MRI, when getting the Location for an eval()'d stack, the #label is set as the enclosing method.

Testcase:

puts RUBY_DESCRIPTION

def test
  eval(
    <<-'CODE'
      location = Thread.current.backtrace_locations[1]
      puts "#base_label '#{location.base_label}', #label '#{location.label}', #to_s '#{location}'"
    CODE
  )
end

test

Output on MRI:

ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux]
#label 'test', #to_s '(eval):1:in `test''

Actual Behavior

JRuby just returns <eval> for both #label (and #base_label):

jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 Java HotSpot(TM) 64-Bit Server VM 25.171-b11 on 1.8.0_171-b11 +jit [linux-x86_64]
#label '<eval>', #to_s '(eval):1:in `<eval>''

If it would be helpful I can also submit a testcase to RubySpec.