21:19:46 <danmcd> Dumb question:  if a kernel thread is "FREE" is it actually such that I can't trust its ::findstack output?
21:19:58 <danmcd> I have a dump with a "FREE" thread with a MASSIVE stack that makes me afraid it overflowed.
21:29:05 <richlowe> is the stack believable?
21:29:19 <richlowe> are you on a build where ::stackinfo works?
21:30:13 <tsoome> default stack is 5 pages? 
21:32:49 <richlowe> I guess you can't get stackinfo after a thread is gone
21:34:07 <richlowe> but yeah, the stack is potentially valid
21:34:19 <richlowe> I don't _think_ it's guaranteed, but it might be
21:53:28 <danmcd>  kmem_stackinfo isn't turned on anyway according to my mdb.
21:54:27 <danmcd> Oh wait.. .NVM.
21:56:24 <richlowe> what's the stack, it should be easy enough to find what's pushing it
21:56:29 <richlowe> andy added the good stuff to $C too
21:56:55 <richlowe> ::stack -sv
21:56:57 <andyf> Oh yes, the `-s` flag is probably useful
22:01:15 <danmcd> Yeah... it's not an overflow by a long shot.  :(