I''m looking for an easy way to use dtrace on _init() for a kernel module but hitting some roadblocks. This doesn''t work: ::xxx:_init { self->follow=1; } :::_fini { self->follow=0; } Because there''s no "xxx" when dtrace runs. The best way I can see is to use fbt:modinstall:entry, tell dtrace about the modctl struct and match by the name of the module. Can we have a new dtrace provider in modctl.c and friends to make this task a bit simpler? Or am I missing something else that''s obvious? Whilst this would appear to fall under the anonymous tracing paradigm, I don''t see why I should have to reboot to debug the _init() of a module that loads well after boot or is optional. This message posted from opensolaris.org