1The following are examples of the results of running the rb_calls.d script. 2 3This script traces activity from all Ruby programs on the system that are 4running with Ruby provider support. In this example we see it running while 5the Code/Ruby/func_abc.rb script is run. 6 7# rb_calls.d 8Tracing... Hit Ctrl-C to end. 9^C 10 FILE TYPE NAME CALLS 11 . obj-new NoMemoryError 1 12 . obj-new SystemStackError 1 13 . obj-new ThreadGroup 1 14 . obj-new fatal 1 15 func_abc.rb method Object::func_a 1 16 func_abc.rb method Object::func_b 1 17 func_abc.rb method Object::func_c 1 18 . obj-new Object 3 19 func_abc.rb method IO::write 3 20 func_abc.rb method Module::method_added 3 21 func_abc.rb method Object::print 3 22 func_abc.rb method Object::sleep 3 23 24We can see that the file func_abc.rb called each of the user-defined functions 25included in the script; func_a, func_b, and func_c. It also called the print 26object and sleep amongst other things. Interspersed in the output are calls 27to new objects that are not tied to the program func_abc.rb. They are called 28from the Ruby engine for some other reason. 29 30