Ruby DTrace (on OSX Leopard)

ruby-talk
1

Has anyone had any luck getting it to run?

Neither Instruments nor dtrace -l shows up any of the Joyent probes
that are supposed to be there. I guess I'm just doing something wrong,
but I can only find little blog articles with people cheering that OSX
contains DTrace, no examples of it actually in use.

Running the example script in /Developer/Examples/Ruby/DTrace yield me:

dtrace: failed to compile script ./print_calls.d: line 4: probe
description ruby*:::function-entry does not match any probes

Any ideas?
   -tim

2

Neither Instruments nor dtrace -l shows up any of the Joyent probes
that are supposed to be there. I guess I'm just doing something wrong,
but I can only find little blog articles with people cheering that OSX
contains DTrace, no examples of it actually in use.

Preliminary experiments show that I need to hook dtrace up with a
running ruby instance. D'uh.
Maybe I should read the documentation... E.g. this:

dtrace -s print_memory_usage.d -p <pid of ruby interpreter>

works, in case someone else couldn't figure it out.
   -tim

3

Tim Becker wrote in post #579367:

Has anyone had any luck getting it to run?

I was able to run it by referring to
http://www.ploughthroughruby.co.uk/2013/04/10/dtrace-probes-in-ruby-2.html/\.
When you are running it remember to change
sudo dtrace -c 'ruby test.rb' -Zn 'ruby*::method-entry {
@[copyinstr(arg0)] = count(); }'
with ruby*:::method-entry

···

Neither Instruments nor dtrace -l shows up any of the Joyent probes
that are supposed to be there. I guess I'm just doing something wrong,
but I can only find little blog articles with people cheering that OSX
contains DTrace, no examples of it actually in use.

Running the example script in /Developer/Examples/Ruby/DTrace yield me:

dtrace: failed to compile script ./print_calls.d: line 4: probe
description ruby*:::function-entry does not match any probes

Any ideas?
   -tim

--
Posted via http://www.ruby-forum.com/\.

4

Tim Becker wrote in post #579384:

Neither Instruments nor dtrace -l shows up any of the Joyent probes
that are supposed to be there. I guess I'm just doing something wrong,
but I can only find little blog articles with people cheering that OSX
contains DTrace, no examples of it actually in use.

Preliminary experiments show that I need to hook dtrace up with a
running ruby instance. D'uh.
Maybe I should read the documentation... E.g. this:

dtrace -s print_memory_usage.d -p <pid of ruby interpreter>

works, in case someone else couldn't figure it out.

Is there any way of making
dtrace -q -s x.d -c'ruby rubyfile.rb'
to work??
Where can I find the documentation??

···

--
Posted via http://www.ruby-forum.com/\.