Adam,
again our views are different. Must be our heritage ;^)
Why was this header file creation invented given that the manual, in the
chapter of statically defined probes for applications, only mentions the
macro's DTRACE_PROBExxx?
I have the impression that the misunderstanding starts with
On Fri, Feb 01, 2008 at 12:11:52AM -0800, Paul van den Bogaard wrote:
Why was this header file creation invented given that the manual, in
the chapter of statically defined probes for applications, only
mentions the macro's DTRACE_PROBExxx?
The header file generation was developed both to
reading the line
$probename =~ s/__/_/g;
in dheadgen.pl it looks like the hack is simple.
Is this perl script part of the distribution or a prototype?
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
I see that rm(1) uses unlinkat(2), but I don't see a syscall provider
probe for unlinkat(2). That's... annoying (but there's always the fbt
provider).
Actually, I don't see any syscall provider probes for any of the
open/unlink/rename/...at[64]() system calls. Is there a CR for this?
Nico
--
On Fri, Feb 01, 2008 at 01:09:22PM -0500, James Carlson wrote:
Nicolas Williams writes:
I see that rm(1) uses unlinkat(2), but I don't see a syscall provider
probe for unlinkat(2). That's... annoying (but there's always the fbt
provider).
Actually, I don't see any syscall provider
