Qiang Liu wrote: > The Solaris Dtrace guide says "The most common use of anonymous tracing is to > permit device driver developers to debug and trace activity that occurs > during system boot" > The anonymous tracing worked fine if my device is not the boot device. > > What if the device driver I want to debug using anonymous tracing happens to > be the driver that control the boot device? So I tried to create an anonymous > enabling following the Dtrace guide and /etc/system was modified to have some > necessary forceload statements added. > > The problem is that the dtrace driver was loaded way after my driver was > loaded and attached and did its work. Obviously forceload xxx in /etc/system > for anonymous tracing is not enough. I guess I have to make my boot device > driver dependent on all these modules(driver) using -dy -N to make sure they > are all loaded before my HBA driver got loaded. > > Any suggestions?
probably can't do that. _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
