goinsane wrote: >> "fbt" is "function based tracing." I'd expect that >> the 'documentation' >> of these is essentially the source code itself. >> > > That's right. A understanding of the source seems essential. Unfortunately > I'm feeling lost between thousands of symbols, typedefs and lines of code.
Well, at least in the US we've got a long weekend coming. Time to study. ;-} Seriously, though, there are some books that may be helpful. "The Magic Garden Explained" does a pretty good job of explaining the internals of System V Release 4, which is at least the basis for much of OpenSolaris. There's no substitute, though, for reading the code. One really good way to learn how the code works is to trouble-shoot a problem. You'll be motivated (and forced) to figure out what the code is doing. Another good way to get going is to look at other D scripts that folks have written. You can find quite a few by searching the web (in addition to the ones in /usr/demo/dtrace). If you don't feel that's a good path for you, then you might want to search around for layered tools built on top of dtrace and/or consultants who can help with the task you have at hand. -- James Carlson 42.703N 71.076W <carls...@workingcode.com> _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
