Apologies for a delayed response.
Chris,
You are right ! Looks like the ruby-CSW does have the dtrace-probes.two
binaries :
-- snip --
bash-3.2$ nm /var/tmp/ruby-x86 | grep dtrace
[1616] | 134982572| 10|FUNC |LOCL |0 |10 |ruby_dtrace_fir
bash-3.2$ nm Desktop/ruby-CSW | grep dtrace
[51] | 134685956| 5821|FUNC |LOCL |2 |13
|$dtrace11297.rb_call0
[49] | 134666000| 19954|FUNC |LOCL |2 |13
|$dtrace11297.rb_eval
[52] | 134699996| 892|FUNC |LOCL |2 |13
|$dtrace11297.rb_longjmp
[53] | 134784196| 4886|FUNC |LOCL |2 |13
|$dtrace11299.garbage_collect
[50] | 135188840| 54|FUNC |LOCL |2 |13
|$dtrace11322.ruby_dtrace_fire
[76] | 0| 0|FILE |LOCL |0 |ABS |dtrace.o
[83] | 134636188| 149|FUNC |LOCL |0 |13 |dtrace_dof_fini
[80] | 134635600| 588|FUNC |LOCL |0 |13 |dtrace_dof_init
[1416] | 135188840| 54|FUNC |LOCL |0 |13 |ruby_dtrace_fire
-- snip --
Thanks again to all of you who responded to this query !
Regards,
Sanjeev.
Chris Andrews wrote:
> 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]
>
_______________________________________________
dtrace-discuss mailing list
[email protected]