[lkml]   [2001]   [May]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [CHECKER] large stack variables (>=1K) in 2.4.4 and 2.4.4-ac8
    On Fri, 25 May 2001 01:33:03 +0200, 
    Andi Kleen <> wrote:
    >On Thu, May 24, 2001 at 05:08:40PM -0600, Andreas Dilger wrote:
    >> I'm curious about this stack checker. Does it check for a single
    >> stack allocation >= 1024 bytes, or does it also check for several
    >> individual, smaller allocations which total >= 1024 bytes inside
    >> a single function? That would be equally useful.
    >At one time someone had a script to grep objdump -S vmlinux for the
    >stack allocations generated by gcc and check them. ix86 specific, probably gcc
    specific and it only picks up code that you compile. The Stanford
    checker is much better.

    >> On a side note, does anyone know if the kernel does checking if the
    >> stack overflowed at any time?
    >You normally get a silent hang or worse a stack fault exception
    >(which linux/x86 without kdb cannot recover from) which gives you instant

    You cannot recover from a kernel stack overflow even with kdb. The
    exception handler and kdb use the stack that just overflowed.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 12:53    [W:0.044 / U:0.272 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site