Comments on: DTrace support for Ruby pre-compiled into Leopard http://leenux.org.uk/2007/10/25/dtrace-support-for-ruby-pre-compiled-into-leopard/ Desktop, Mobile and Server Side Solutions Thu, 29 Jul 2010 02:22:19 +0000 hourly 1 http://wordpress.org/?v=abc By: V http://leenux.org.uk/2007/10/25/dtrace-support-for-ruby-pre-compiled-into-leopard/comment-page-1/#comment-17 V Wed, 31 Oct 2007 06:26:54 +0000 http://blog.leenux.org.uk/2007/10/25/dtrace-support-for-ruby-pre-compiled-into-leopard/#comment-17 <p>And Ruby has to be running for the probes to show up.</p> And Ruby has to be running for the probes to show up.

]]> By: Lee http://leenux.org.uk/2007/10/25/dtrace-support-for-ruby-pre-compiled-into-leopard/comment-page-1/#comment-16 Lee Tue, 30 Oct 2007 12:24:30 +0000 http://blog.leenux.org.uk/2007/10/25/dtrace-support-for-ruby-pre-compiled-into-leopard/#comment-16 <p>(You have to be using Ruby that comes with Leopard - the one installed with Macports might be in your path first)</p> (You have to be using Ruby that comes with Leopard – the one installed with Macports might be in your path first)

]]> By: Lee http://leenux.org.uk/2007/10/25/dtrace-support-for-ruby-pre-compiled-into-leopard/comment-page-1/#comment-15 Lee Tue, 30 Oct 2007 12:23:56 +0000 http://blog.leenux.org.uk/2007/10/25/dtrace-support-for-ruby-pre-compiled-into-leopard/#comment-15 <p>18698 ruby6202 libruby.1.dylib rb_call0 function-entry<br /> 18699 ruby6202 libruby.1.dylib rb_call0 function-return<br /> 18700 ruby6202 libruby.1.dylib garbage_collect gc-begin<br /> 18701 ruby6202 libruby.1.dylib garbage_collect gc-end<br /> 18702 ruby6202 libruby.1.dylib rb_eval line<br /> 18703 ruby6202 libruby.1.dylib rb_obj_alloc object-create-done<br /> 18704 ruby6202 libruby.1.dylib rb_obj_alloc object-create-start<br /> 18705 ruby6202 libruby.1.dylib garbage_collect object-free<br /> 18706 ruby6202 libruby.1.dylib rb_longjmp raise<br /> 18707 ruby6202 libruby.1.dylib rb_eval rescue<br /> 18708 ruby6202 libruby.1.dylib ruby_dtrace_probe ruby-probe</p> 18698 ruby6202 libruby.1.dylib rb_call0 function-entry
18699 ruby6202 libruby.1.dylib rb_call0 function-return
18700 ruby6202 libruby.1.dylib garbage_collect gc-begin
18701 ruby6202 libruby.1.dylib garbage_collect gc-end
18702 ruby6202 libruby.1.dylib rb_eval line
18703 ruby6202 libruby.1.dylib rb_obj_alloc object-create-done
18704 ruby6202 libruby.1.dylib rb_obj_alloc object-create-start
18705 ruby6202 libruby.1.dylib garbage_collect object-free
18706 ruby6202 libruby.1.dylib rb_longjmp raise
18707 ruby6202 libruby.1.dylib rb_eval rescue
18708 ruby6202 libruby.1.dylib ruby_dtrace_probe ruby-probe

]]> By: a2800276 http://leenux.org.uk/2007/10/25/dtrace-support-for-ruby-pre-compiled-into-leopard/comment-page-1/#comment-14 a2800276 Tue, 30 Oct 2007 12:20:44 +0000 http://blog.leenux.org.uk/2007/10/25/dtrace-support-for-ruby-pre-compiled-into-leopard/#comment-14 <p>Could you provide a short example of how you're calling Dtrace? Dtrace -l doesn't show me any of the Joyent probes and trying to run the example scripts in /Dev.../Examples/Ruby/DTrace yields:</p> <p><br /> "probe description ruby*:::function-entry does not match any probes"</p> Could you provide a short example of how you’re calling Dtrace? Dtrace -l doesn’t show me any of the Joyent probes and trying to run the example scripts in /Dev…/Examples/Ruby/DTrace yields:

“probe description ruby*:::function-entry does not match any probes”

]]> By: V http://leenux.org.uk/2007/10/25/dtrace-support-for-ruby-pre-compiled-into-leopard/comment-page-1/#comment-13 V Mon, 29 Oct 2007 06:35:57 +0000 http://blog.leenux.org.uk/2007/10/25/dtrace-support-for-ruby-pre-compiled-into-leopard/#comment-13 <p>For me arg0 is the filename, arg1 is the parent of the function called and arg2 is the line number.</p> <p>It's a bit odd that it shows the parent and not the actual function being called.</p> For me arg0 is the filename, arg1 is the parent of the function called and arg2 is the line number.

It’s a bit odd that it shows the parent and not the actual function being called.

]]> By: Lee http://leenux.org.uk/2007/10/25/dtrace-support-for-ruby-pre-compiled-into-leopard/comment-page-1/#comment-12 Lee Sun, 28 Oct 2007 19:19:53 +0000 http://blog.leenux.org.uk/2007/10/25/dtrace-support-for-ruby-pre-compiled-into-leopard/#comment-12 <p>Python on Leopard has the evaluator entries which are all there really is. On Solaris it had more, but they weren't actually needed, if I remember correctly.</p> <p>However - I think the Python in OSX is broken in that respect. Cos I can't get the line numbers out. I can get method name (arg1), filename (arg2) but not the line number.</p> Python on Leopard has the evaluator entries which are all there really is. On Solaris it had more, but they weren’t actually needed, if I remember correctly.

However – I think the Python in OSX is broken in that respect. Cos I can’t get the line numbers out. I can get method name (arg1), filename (arg2) but not the line number.

]]> By: V http://leenux.org.uk/2007/10/25/dtrace-support-for-ruby-pre-compiled-into-leopard/comment-page-1/#comment-11 V Sun, 28 Oct 2007 19:02:23 +0000 http://blog.leenux.org.uk/2007/10/25/dtrace-support-for-ruby-pre-compiled-into-leopard/#comment-11 <p>Hi,</p> <p>I'm just trying out DTrace on Leopard, but there isn't any Python providers, except for the evaluator entries (PyEval_EvalFrameEx:entry). I was expecting to see function-entry etc. providers.</p> <p>Does Python have function-entr on your system?</p> <p>I might have some problems with Python versions, as I upgraded from Tiger, which had MacPython 2.5 installed. Could you print Python version and build, plus all Python DTrace providers.</p> <p>PS: Provider might be the wrong term, please forgive me for that, I'm a DTrace newbie.<br /> --V</p> Hi,

I’m just trying out DTrace on Leopard, but there isn’t any Python providers, except for the evaluator entries (PyEval_EvalFrameEx:entry). I was expecting to see function-entry etc. providers.

Does Python have function-entr on your system?

I might have some problems with Python versions, as I upgraded from Tiger, which had MacPython 2.5 installed. Could you print Python version and build, plus all Python DTrace providers.

PS: Provider might be the wrong term, please forgive me for that, I’m a DTrace newbie.
–V

]]>