Issue #7976 has been updated by jeremyevans0 (Jeremy Evans). Status changed from Assigned to Closed @headius and I agree this is not a bug. JRuby has similar behavior for Java extensions as CRuby does for C extensions. ---------------------------------------- Bug #7976: TracePoint call is at call point, not call site https://bugs.ruby-lang.org/issues/7976#change-103024 * Author: zenspider (Ryan Davis) * Status: Closed * Priority: Normal * Assignee: ko1 (Koichi Sasada) * ruby -v: 2.0 ---------------------------------------- Using TracePoint to make a new tracer utility I'm finding it very difficult to actually trace where the origin is for type :call. Instead, I get the destination. This is not the case for :c_call or :b_call as they trace at the origin, not destination. Reproduction attached. Notice how it outputs ":call wtf.rb:08 :x" where line 8 is the definition of x, not the call of x, yet the subsequent backtrace lists line 21 which is the original origin for the call to x. ---Files-------------------------------- tp_test.rb (1.21 KB) -- https://bugs.ruby-lang.org/