Issue #3660 has been updated by Keiju Ishitsuka.

Status changed from Assigned to Rejected

These trace messages is spec that ignore c-func and c-return event, now.

If you want to print c-func and c-return event, please set:

  Tracer::display_c_call = true

----------------------------------------
Bug #3660: Trace events seem to be missing
http://redmine.ruby-lang.org/issues/3660

Author: Roger Pack
Status: Rejected
Priority: Normal
Assignee: Keiju Ishitsuka
Category: 
Target version: 1.9.3
ruby -v: ruby 1.9.3dev (2010-07-22 trunk 28717) [i386-mingw32]


=begin
 When tracing this code:
 
 a = [1,2,3]
 a.each{|n|
   p n
 }
 
 with 1.9.1 I get "expected output" list this:
 
 http://gist.github.com/506859
 
 However, with 1.9.2+ I get almost no output:
 
 C:\dev\ruby\ruby-prof>ruby -vrtracer test_array.rb
 ruby 1.9.2dev (2010-07-02) [i386-mingw32]
 #0:test_array.rb:1::-: a = [1,2,3]
 #0:test_array.rb:2::-: a.each{|n|
 #0:test_array.rb:3::-:   p n
 1
 #0:test_array.rb:3::-:   p n
 2
 #0:test_array.rb:3::-:   p n
 3
 
 This on windows and Linux.
 Unless it's expected, in which case it's just missing the return statement.
 Thanks.
 -r
=end



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