On Tue, Jun 17, 2008 at 01:57:20PM -0700, James McIlree wrote:
> > Now the problems start: I meant to pass in high-level information into
> > the probe, because that will maximize the flexibility of writing
> > scripts.
> > But now writing a D script that makes use of con means either
> > - including the structs and enums in the script
> > - including the original header file and using that
> > - doing lots and lots of error prone copyin(arg2 + xxx,
> > sizeof(type)), which is neither elegant nor nice on the script author
> >
> > Because 'typedef struct { ... } network_mysqld_con' is actually a non-
> > trivial struct and refers to various other structs and enums it's not
> > a good idea to copy it in. Things _will_ get out of sync.
>
> At first glance, it seems like user space CTF would be a big
> win here.
Well, the easiest fix is to do one, or both, of fixing system headers to
be DTrace-friendly (hello, Solaris stat_impl.h), or improving the
DTrace parser to understand such headers and ignore the relevant bits
regards
john
_______________________________________________
dtrace-discuss mailing list
[email protected]
