Dan Mick wrote:
> Alexander Kolbasov wrote:
>
>> You can do something like this:
>>
>> 0x3000a1733a8::print queue_t q_first | ::walk b_next|::walk b_cont|
>> ::print mblk_t b_rptr | /s
>
> boy, it would be nice to know what the various walkers take as input and
> what they generate as output; the "::walkers" output just doesn't cut it.
> Is there some "walkers help" that I'm looking past?
Not that I'm aware of. It would certainly make life a lot easier
in general if people writing walkers would include that information
in the help text. Am I preaching to the choir?
James C. McPherson
--
Solaris kernel software engineer, system admin and troubleshooter
http://www.jmcp.homeunix.com/blog
Find me on LinkedIn @ http://www.linkedin.com/in/jamescmcpherson
