<headius> ok first major snag with this approach... c_call and c_return depend on interpreter backtrace to get file and line
<headius> so they are probably not even working right currently once a method jits
<headius> well I have always-on call, return, b_call, and b_return, and can confirm they are eliminated in C2 when no hooks are enabled
<headius> not sure this is the right approach though since c_call and c_return can't be always on without requiring backtraces
<headius> might have to move this into the call sites anyway
genpaku has quit [Remote host closed the connection]
genpaku has joined #jruby
<headius> Only a few failures from always on hooks 👍
<headius> Still need a plan for c_call and c_return though