On Wed, Sep 07, 2005 at 10:18:13AM +0200, Michal Schmidt wrote: > nazim khan wrote: > >I suspect that one of my module that I am inserting in > >the kernel may be causing the stack overflow which is > >leading to kernel crash (may because it is corrupting > >some one lese memory). > > > >How can I find this out? > > You could enable CONFIG_DEBUG_STACKOVERFLOW. > If you showed us your module's source code, someone might see the bug. > > Michal > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/
Additionally, if you have netconsole/netdump set up, you can examine the resultant core file with the crash utility to find telltale signs of an overflow. Nominally a stack overflow results in the corruption of data at the end of a neighboring task_struct. Regards Neil -- /*************************************************** *Neil Horman *Software Engineer *gpg keyid: 1024D / 0x92A74FA1 - http://pgp.mit.edu ***************************************************/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
