On Tue, Nov 27, 2007 at 11:51:05AM -0500, Angelo Rajadurai wrote:
> Looks like Leopard perl executable does have perl probes but they are
> different from the once listed in
> http://blogs.sun.com/alanbur/entry/dtrace_and_perl
>
> Here is what I did.
>
> On one terminal ran perl and on another ran
>
> $ ps -ef | grep perl
> 501 4385 4373 0 0:00.01 ttys000 0:00.01 perl
>
> $ sudo dtrace -l -n perl4385:::
> ID PROVIDER MODULE FUNCTION
> NAME
> 18659 perl4385 libperl.dylib Perl_pp_sort
> entry
> 18660 perl4385 libperl.dylib Perl_pp_dbstate
> entry
> 18661 perl4385 libperl.dylib Perl_pp_entersub
> entry
> 18662 perl4385 libperl.dylib Perl_pp_last
> exit
> 18663 perl4385 libperl.dylib Perl_pp_return
> exit
> 18664 perl4385 libperl.dylib Perl_dounwind
> exit
> 18665 perl4385 libperl.dylib Perl_pp_leavesublv
> exit
> 18666 perl4385 libperl.dylib Perl_pp_leavesub
> exit
>
> Alan's blog talks about sub-entry and sub-return probes which do not
> exist in Leopards version of the probes.
We're not sure why the entry probes are named "entry" (instead of "sub-entry",
which is much truer to both DTrace and Perl) and -- more gallingly -- why
the return probes are named "exit". (DTrace historians will recall that
this particular issue was one of considerable deliberation, with a vestigal
version of the syscall provider -- nee "systrace" -- having "exit" instead
of "return" probes from its introduction in d10_16 through to its
rechristening in d10_18. But I digress...)
> May be the apple folks can clarify.
We have an open question to Apple on this issue. James agreed that it
was odd, and is following up with the responsible engineer. James,
perhaps you could send your findings to dtrace-discuss?
- Bryan
--------------------------------------------------------------------------
Bryan Cantrill, Sun Microsystems FishWorks. http://blogs.sun.com/bmc
_______________________________________________
dtrace-discuss mailing list
[email protected]
