> [ I posted this a week ago, but haven't seen any response. > > Now that the DTrace "movers and shakers" are done setting > up dtrace.conf(8) (and a fine unconference it was!), can > someone give me some direction in setting up some pages? > > Who knows, maybe others will follow my lead and post their > own "wish list" items... -r ]
I posted reply, but don't recall seeing it here. My wishlist:
6496550 DTrace needs a way to get time linear sequential output on multi-cpu
systems.
- if you have more than one cpu core, dtrace output is just a mess. You
have to trace(timestamp) in every probe and later sort the output by
cat output | sed -e 's/^ *[^ ]* *[^ ]* *//' | sort -n +1 > sorted
6314638 Dtrace needs a packet dumper
- if you ever tried to dump mblk_t structures in streams module, you
know what I'm talking about
5059507 watchpoint provider
- That would be nice, but falls a bit out of dtrace scope, as the
probes would have to be generated during dtrace run. But how sweet
would be this?
pid$target::malloc:entry
/self->is_inside_my_function/
{
self->x = 1;
}
pid$target::malloc:return
/self->is_inside_my_function && self->x/
{
add_watchpoint("my_memory", arg0, 10)
}
watchpoint:my_memory:write:entry
{
printf("Culprit ! Memory %p is being changed\n", arg0);
printf("Previous value = %c", stringof(copyin(arg0, 1)));
ustack();
}
watchpoint:my_memory:write:return
{
printf("new value = %c", stringof(copyin(arg0, 1)));
}
Thanks
--
Vlad
pgpc8TOXI1aaZ.pgp
Description: PGP signature
_______________________________________________ dtrace-discuss mailing list [email protected]
