> On Wed, Aug 27, 2008 at 08:35:44PM +0300, Adrian Bunk wrote:> > CONFIG_DEBUG_STACKOVERFLOW should give you the same information, and if> > wanted with an arbitrary limit.>> In some cases, yes. In the CONFIG_DEBUG_STACKOVERFLOW case the check is> only performed from do_IRQ(), which is sporadic at best, especially on> tickless. While it catches some things, it's not a complete solution in> and of iteslf.

BTW, on sparc64 we have a stack overflow checker that runs viathe profiling _mcount hook. So every function call we checkif the stack is getting overused.

If so, we jump onto a special static debugging stack and printthe stack overflow message.

And yes it works with IRQ stacks which is all that sparc64 usesnowadays.