Re: CONFIG_DEBUG_STACKOVERFLOW hurts

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

_______________________________________________
Fedora-kernel-list mailing list
Fedora-kernel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-kernel-list

[Index of Archives]     [Fedora General Discussion]     [Older Fedora Users Archive]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [USB]     [Asterisk PBX]

  Powered by Linux