https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112010-08-26T23:15:34ZRuby Issue Tracking SystemRuby master - Bug #3660: Trace events seem to be missinghttps://bugs.ruby-lang.org/issues/3660?journal_id=129922010-08-26T23:15:34Zrogerdpack (Roger Pack)rogerpack2005@gmail.com
<ul></ul><p>=begin<br>
still the case with ruby 1.9.3dev (2010-08-26 trunk 29104) [i386-mingw32]<br>
=end</p> Ruby master - Bug #3660: Trace events seem to be missinghttps://bugs.ruby-lang.org/issues/3660?journal_id=130342010-08-27T13:24:02Zshyouhei (Shyouhei Urabe)shyouhei@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Assigned</i></li><li><strong>Assignee</strong> set to <i>ko1 (Koichi Sasada)</i></li></ul><p>=begin</p>
<p>=end</p> Ruby master - Bug #3660: Trace events seem to be missinghttps://bugs.ruby-lang.org/issues/3660?journal_id=134682010-09-19T13:27:22Zwanabe (_ wanabe)s.wanabe@gmail.com
<ul><li><strong>Assignee</strong> changed from <i>ko1 (Koichi Sasada)</i> to <i>keiju (Keiju Ishitsuka)</i></li></ul><p>=begin<br>
It is intended. see r24226.<br>
But I don't know the reason of this change.</p>
<p>Keiju, I would appreciate it if you could explain why.<br>
=end</p> Ruby master - Bug #3660: Trace events seem to be missinghttps://bugs.ruby-lang.org/issues/3660?journal_id=158272011-02-15T12:28:49Zrocky (Rocky Bernstein)rocky@gnu.org
<ul></ul><p>=begin<br>
I think this was fixed by r29914 which changes</p>
<pre><code>elsif caller.size <= 1
</code></pre>
<p>to:</p>
<pre><code>elsif caller.count {|bt| /\A<internal:[^<>]+>:/ !~ bt} <= 1
</code></pre>
<p>=end</p> Ruby master - Bug #3660: Trace events seem to be missinghttps://bugs.ruby-lang.org/issues/3660?journal_id=158562011-02-17T06:48:01Zheadius (Charles Nutter)headius@headius.com
<ul></ul><p>=begin<br>
It's worth mentioning that tracer is broken in JRuby for the same reason. Depending on caller to be the same all the time is a bit fragile. Ideally there'd be a better marker for whether tracer should be started up right away or not.<br>
=end</p> Ruby master - Bug #3660: Trace events seem to be missinghttps://bugs.ruby-lang.org/issues/3660?journal_id=159072011-02-22T04:29:30Zrogerdpack (Roger Pack)rogerpack2005@gmail.com
<ul></ul><p>=begin<br>
This isn't actually a problem with "-rtracer" not turning Tracer.on, it's that it does output, but outputs far fewer symbols (mostly missing tons of returns).<br>
Cheers!<br>
-r<br>
=end</p> Ruby master - Bug #3660: Trace events seem to be missinghttps://bugs.ruby-lang.org/issues/3660?journal_id=162592011-03-31T23:32:44Zrogerdpack (Roger Pack)rogerpack2005@gmail.com
<ul></ul><p>=begin<br>
Keiju was this expected? I'm thinking it wasn't...<br>
=end</p> Ruby master - Bug #3660: Trace events seem to be missinghttps://bugs.ruby-lang.org/issues/3660?journal_id=183822011-06-26T17:10:04Znahi (Hiroshi Nakamura)nakahiro@gmail.com
<ul><li><strong>Target version</strong> set to <i>1.9.3</i></li></ul> Ruby master - Bug #3660: Trace events seem to be missinghttps://bugs.ruby-lang.org/issues/3660?journal_id=186402011-06-28T23:52:50Zkeiju (Keiju Ishitsuka)keiju@ishitsuka.com
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Rejected</i></li></ul><p>These trace messages is spec that ignore c-func and c-return event, now.</p>
<p>If you want to print c-func and c-return event, please set:</p>
<p>Tracer::display_c_call = true</p> Ruby master - Bug #3660: Trace events seem to be missinghttps://bugs.ruby-lang.org/issues/3660?journal_id=266432012-05-16T02:23:17ZAnonymous
<ul></ul><blockquote>
<p>If you want to print c-func and c-return event, please set:</p>
<p> Tracer::display_c_call = true<br>
...<br>
However, with 1.9.2+ I get almost no output:</p>
<p> C:\dev\ruby\ruby-prof>ruby -vrtracer test_array.rb<br>
ruby 1.9.2dev (2010-07-02) [i386-mingw32]<br>
#0:test_array.rb:1::-: a = [1,2,3]<br>
#0:test_array.rb:2::-: a.each{|n|<br>
#0:test_array.rb:3::-: p n<br>
1<br>
#0:test_array.rb:3::-: p n<br>
2<br>
#0:test_array.rb:3::-: p n<br>
3</p>
</blockquote>
<p>It works.<br>
Still seems a bit odd to me that it doesn't appear to log a "return"<br>
call from the #each method unless you have display_c_call turned on<br>
[?]</p>