From: Paul Mundt <lethal@xxxxxxxxxxxx> Date: Thu, 28 Aug 2008 09:32:13 +0900 > 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 via the profiling _mcount hook. So every function call we check if the stack is getting overused. If so, we jump onto a special static debugging stack and print the stack overflow message. And yes it works with IRQ stacks which is all that sparc64 uses nowadays. Perhaps this is useful enough to make generic. -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
