On Jun 17, 2008, at 4:47 AM, Kay Röpke 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.
James M
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
