From: "deivid (David Rodríguez)" <deivid.rodriguez@...>
Date: 2013-06-30T21:26:34+09:00
Subject: [ruby-core:55711] [ruby-trunk - Bug #7976] TracePoint call is at call point, not call site


Issue #7976 has been updated by deivid (David Rodr��guez).


I find this behaviour satisfactory for my purposes.

If I need the origin of a :call event I use the previous :line event. Is this wrong?
----------------------------------------
Bug #7976: TracePoint call is at call point, not call site
https://bugs.ruby-lang.org/issues/7976#change-40205

Author: zenspider (Ryan Davis)
Status: Open
Priority: Normal
Assignee: ko1 (Koichi Sasada)
Category: core
Target version: 
ruby -v: 2.0
Backport: 


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.


-- 
http://bugs.ruby-lang.org/