Interesting. My expectation was that it would work like gdb i.e. that the
app would not run until gdb was in full control. For me, -c implies that
behavior.
I tried putting in a sleep for 10 seconds; still nothing:
$ sudo dtrace -n 'pid$target:::entry { trace(arg0); }' -c ./out
On Tue, Dec
I am cross-posting back to dtrace-discuss, since the Apple folks listen...
I'm not sure what your hello world program is doing. I tried the same thing
with compiled C code.
The problem I ran into with hello world, and with the date example, is
the program is executing and completing before dtrac
When you say "straight from the dtrace book", I assume you mean
the soon-to-be-published book?
If that is the case, please allow me to clarify. Not every invocation of dtrace,
both one-liners and scripts, that are in the book (and there are hundreds) is
tested and guaranteed to work under all thr
Under osx 10.6.5:
~ $ sudo dtrace -n 'pid$target:libc::entry { @[probefunc] = count(); }' -c
date
Tue Dec 7 11:40:59 PST 2010
dtrace: invalid probe specifier pid$target:libc::entry { @[probefunc] =
count(); }: probe description pid94942:libc::entry does not match any probes
This is an example st
