http://tldp.org/LDP/lkmpg/2.6/html/x861.html http://lwn.net/Articles/22355/ BRs Lin 2009/9/3 Robert P. J. Day <rpjday@xxxxxxxxxxxxxx>: > > was in the midst of writing my final installment of newbie column > for how to use /proc sequence files for debugging, and suddenly i'm > not convinced i know every detail about them. in particular, i'm > looking at the prototype for the "stop" routine: > > void stop(struct seq_file* s, void* v); > > and the question is: what is it that one should expect in the "v" > parameter when the relevant stop() routine is invoked? > > specifically, i wrote an example that generates so much output that > the start() routine is invoked a number of times to keep restarting > the output at various points, and all that works just fine. > > but it *seems* that, at each *intermediate* call to the stop > routine, "v" will contain the current void pointer to whatever it is > you want to point at. but in the *final* call to the stop routine to > really terminate the output, that pointer value is *null*. > > that just seems weird, and i can't find documentation that really > and truly describes the mechanics. perhaps i'll post the code > shortly, and people can test it. that will, of course, spoil the > surprise of the next column, but i'd rather be right than surprising. > > rday > -- > > ======================================================================== > Robert P. J. Day Waterloo, Ontario, CANADA > > Linux Consulting, Training and Annoying Kernel Pedantry. > > Web page: http://crashcourse.ca > Twitter: http://twitter.com/rpjday > ======================================================================== > > -- > To unsubscribe from this list: send an email with > "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx > Please read the FAQ at http://kernelnewbies.org/FAQ > > -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
