Well after a fair amount of head scratching I managed to hack up a
libmod_dtrace.a kernel module.
The main issue (make issues aside) was getting the dtrace resource manager
to play ball with
procnto.  It turns out that you can't use a lot of the iofunc_*default
routines!

So now I have a basic dtrace device running within procnto.  The main
impetus for this was that
I wanted to get the ustack() provider running.  This is arguably one of the
more useful bits
of info you can get, and running the probes in an event handler, you don't
have access to the
user context of the probed process (because the kernel switched the address
space to your
context before calling your function).

Up next - a kercall provider and hopefully then the stack() and ustack()
actions.  Cool bananas!

Oh, and cleaning up my resmgr mess! :-)

Colin

-- 
cburgess@qnx.com