Displaying 2 results from an estimated 2 matches for "copystr".
2006 Jun 30
2
Qs. on fbt::copystr: probe
Hi all,
I have questions about something I observed just now:
1) on AMD64, S10u1:
# dtrace -n ''fbt::copystr:entry{printf ("%p\n", args[0]);}'' -c /bin/pwd
dtrace: invalid probe specifier fbt::copystr:entry{printf ("%p\n",
args[0]);}: in action list: index 0 is out of range for fbt::copystr:entry
args[ ]
but
# dtrace -n ''fbt::copystr:entry{printf ("%p\n",...
2008 Sep 30
12
dtrace missing ''unlinkat''? showing process stack?
everyone,
Just out of curiosity, I did a
dtrace -n ''syscall:::entry { @num[execname, probefunc] = count(); }''
and looked at the entries produced by ''rm''.
I see everything that rm did, *except* the unlinkat - which is unfortunate because I want to trace which processes have deleted which files.
So - does dtrace contain unlinkat as a probe for a system call?