CONFIG_DEBUG_STACKOVERFLOW hurts

[Eric Sandeen]

Gilboa Davara wrote:

>> I like the CONFIG_DEBUG_STACKUSAGE which accurately tells you what your
>> max stack excursions have been.   I just wish it could tell you what the
>> callchain *was* (not really possible, as it's written) - and making it
>> resettable would be nice too (easy).
> 
> /me adds a note to self to lookup the CONFIG_DEBUG_STACKUSAGE code so
> I'll know what you're talking about ;)

Hm it'd be easier to find if I spelled it right: CONFIG_DEBUG_STACK_USAGE :)

It zeros the whole stack when it's allocated.  When a thread exits, it
finds the first non-zero value on the stack, and from that calculates
the max stack excursion.  See check_stack_usage() called from do_exit().

-Eric