On 12/27/06, Michael Shapiro <[EMAIL PROTECTED]> wrote:
> On 12/27/06, Frank Hofmann <[EMAIL PROTECTED]> wrote:
> > On Wed, 27 Dec 2006, Garrett D'Amore wrote:
> >
> > [ ... ]
> > > A better way, IMO, would be to create a new global symbol, "_debug" or
> > > somesuch, that is an integer providing the value. This could be
> > > overridden using the "normal" methods, and would also avoid any
> > > compatibility issues in extending modlinkage.
> >
> > How about a "dprintf DTrace provider" ? I'm dreaming of an interface like
> > this:
>
> How do you want to debug dtrace itself? Is it possible to dtrace via dtrace?
One can dtrace dtrace as in use the kernel framework + command to debug
the command and library. We do this often. One cannot debug DTrace the
kernel software, though, since you can't instrument the kernel portion of
the instrumentation framework. This would violate the s/w laws of physics.
I was thinking about this part. Why is this a violation of physics? A
perfect emulator can run itself like the Russian dolls, over and over
and over and over again in a nested nested nested fashion
--
_ Felix Schulte
_|_|_ mailto:[EMAIL PROTECTED]
(0 0)
ooO--(_)--Ooo
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
