m...@bruningsystems.com wrote:
Hi l1x,
l1x wrote:
Hey, I am wondering how can I enable dtrace probes to ruby
However:
r...@opensolaris:~# dtrace -l | grep -i ruby | wc -l
0
(just to confirm r...@opensolaris:~# dtrace -l | grep -i postgres |
wc -l
55
)
dtrace -l by itself will only show kernel probes. I doubt there are
any probes in
the operating system for ruby or postgres. You might try looking at
http://ruby-dtrace.rubyforge.org/ for an example of using dtrace with
ruby.
(Or, do what I did... search the net for "ruby dtrace probes".
dtrace -l will actually show all currently registered probes including
user land USDT probes.
However an instance of an application with USDT probes has to be running
in order to list it.
For example:
mi...@r600:~# pargs 1353
1353: /usr/bin/python2.4 /usr/lib/updatemanagernotifier
argv[0]: /usr/bin/python2.4
argv[1]: /usr/lib/updatemanagernotifier
mi...@r600:~# dtrace -l | grep python1353
530 python1353 libpython2.4.so.1.0 PyEval_EvalFrame
function-entry
531 python1353 libpython2.4.so.1.0 dtrace_entry
function-entry
532 python1353 libpython2.4.so.1.0 PyEval_EvalFrame
function-return
533 python1353 libpython2.4.so.1.0 dtrace_return
function-return
mi...@r600:~#
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
