On 2/8/08, Sanjeev Bagewadi <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am trying use the ruby provider... but that seems to be failing for
> some reason :
> -- snip --
> dtrace -n 'ruby$target::: {trace(arg0);}' -c /var/tmp/ruby
> dtrace: invalid probe specifier ruby$target::: {trace(arg0);}: probe
> description ruby2063::: does not match any probes
> ...
> -- snip --
>
> I picked up the ruby binary from
> http://svn.joyent.com/opensource/dtrace/ruby/binaries/solaris/ (ie.
> ruby-x86)
It looks like the ruby-x86 binary doesn't actually have DTrace
enabled, whereas the -CSK and -CSW binaries do:
# dtrace -n 'ruby$target:::' -c ./ruby-x86
dtrace: invalid probe specifier ruby$target:::: probe description
ruby7173::: does not match any probes
vs
# dtrace -n 'ruby$target:::' -c ./ruby-CSK
dtrace: description 'ruby$target:::' matched 11 probes
CPU ID FUNCTION:NAME
0 74783 rb_obj_alloc:object-create-start
0 74782 rb_obj_alloc:object-create-done
...
Odd, but perhaps that's what's meant by "standard build" in the README?
Chris.
_______________________________________________
dtrace-discuss mailing list
[email protected]
