You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
while implementing (and trying to test) some Thread#name propagating into the Java thread name, I noticed reported file/line get a little wild on JRuby - e.g. test/unit messes them up (although even without the require 'test/unit' the line number is not correct) :
recall this is smt I've run into in the past as well ... Thread.new sometimes not having a correct line number when looking through VisualVM - although that is not that relevant, since it wasn't much visible. nowdays (since Ruby 2.2) Thread#inspect includes the Thread.new source location so it would be great to have it right.
p.s. also context.getFile gets "" (empty) and context.getLine == 0when JIT-ed
The text was updated successfully, but these errors were encountered:
while implementing (and trying to test) some
Thread#name
propagating into the Java thread name, I noticed reported file/line get a little wild on JRuby - e.g.test/unit
messes them up (although even without therequire 'test/unit'
the line number is not correct) :recall this is smt I've run into in the past as well ...
Thread.new
sometimes not having a correct line number when looking through VisualVM - although that is not that relevant, since it wasn't much visible. nowdays (since Ruby 2.2)Thread#inspect
includes theThread.new
source location so it would be great to have it right.p.s. also
context.getFile
gets""
(empty) andcontext.getLine
==0
when JIT-edThe text was updated successfully, but these errors were encountered: