Tiller,
In this case, its because dtrace believes there is a jump table:
ghopper:/# dtrace -xdebug -l -n 'pid$target::memcpy:' -c /usr/bin/true
[ ... ]
libdtrace DEBUG: grabbed pid 76537 (cached)
libdtrace DEBUG: creating probe pid76537:libSystem.B.dylib:memcpy:*
libdtrace DEBUG:
Hi All,
I have been doing some application tracing on OS X using the pid provider to
trace function entry and returns. I have noticed that some function have
entry probes, but no return probes. In fact, there are not even any
instruction offset probes, only the entry probe. This is unbalancing t
