Kernel#caller behavior is different for files with .rbw extension

Charles Oliver Nutter added a comment - 26/Jan/11 5:50 AM The problem here was how we build backtraces now. We pull off a Java trace, mining out any frames that look like compiled Ruby. Most compiled Ruby frames have a $RUBY$ marker somewhere in them, but the toplevel of a script does not...it's just the class name for the file (usually just the filename) with a method name of _ file _. None of the other markers worked either, since it wasn't -e, wasn't a .rb file, and so on. As a result, we had no marker for that toplevel frame, and it was not included in backtraces or caller. For now, I've added _ file _ as another marker, since it's unlikely to show up in any Java frame (and wouldn't be a huge deal if it did). commit 80ab30ab0b855ac95cee3476c6ce1666a293854c Author: Charles Oliver Nutter <headius@headius.com> Date: Wed Jan 26 05:26:02 2011 -0600 Fix JRUBY-5363 : Kernel#caller behavior is different for files with .rbw extension Add _ file _ method name as a marker for compiled Ruby. Probably should make _ file _ call a $RUBY$-marked method instead, but this is fine for now.