> Eric > Thank you, that is definitely the starting point. > Once we have the driver's context structure pointer, > to dump it out will i have to implement a mdb > extension (Chapter 10 in mdb reference) to dump the > fields of this context structure? > agree, the driver's internal structure is part of > the driver code, what i was hoping for is to be able > to make mdb "aware" of the driver's internal data > structures, similar to the kernel data structures > that are always available. > > Thanks again. > > -Shank
I don't _think_ you necessarily need an mdb module, unless you need something like a "walker" to iterate through a linked list or somesuch. What I think you may need (and I'm out of my depth here, so I could be wrong) is "ctf" - compact debugging information associated with your driver, which might let mdb know the difference between an arbitrary data symbol and one that declared some particular struct, for example. Googling for mdb ctf driver finds (2nd hit) http://blogs.sun.com/jmcp/entry/getting_started_with_your_own1 which appears to describe how to give your driver that ctf debugging info. Be advised the link is _old_, so among other things, there's bound to be a newer version of the file of tools to download. I think that's the real first step to what you want. You may still want custom mdb modules to provide higher-level support, but in addition to, not instead of, the ctf info. -- This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
