Shouldn't; I believe that was for letting dtrace see into what perl is doing (so you'd be able to monitor sub entry/exit and what not at the perl level similar to how you can watch system calls at the kernel level). This snippet from a dtrace FAQ might even be enough:

dtrace -n 'syscall::open*:entry { printf("%s %s",execname,copyinstr(ar
+g0)); }'
[download]

I think last I looked there were some good dtrace intros at opensolaris.org if you want to extend or tweak that to show different stuff.

Update: And as to the original question Devel::Trace might also be of use (although for serious programs it'd be a boatload of output).