lkml.org 
[lkml]   [2012]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [3.4-rc3] Thread overran stack, or stack corrupted
    From
    Date
    On Tue, 2012-04-17 at 23:50 -0400, Dave Jones wrote:

    > > Just to make sure, what does
    > >
    > > /sys/kernel/debug/tracing/enabled_functions
    > >
    > > have?
    >
    > 33503 lines.

    That sounds correct.

    >
    > > This would show what functions the stack tracer is using.
    > >
    > > I just compiled the latest vanilla kernel and tried it out, and it
    > > worked for me.
    >
    > works on my other machines too with similar kernel configs, just not on the one I'm profiling.

    I have to ask. Is this a x86 box?

    Also, have you tested to see if function tracing works?

    # cd /sys/kernel/debug/tracing
    # echo function > current_tracer
    # cat trace

    If function tracing doesn't work this wouldn't either.

    I'm also assuming you have CONFIG_STACKTRACE and
    CONFIG_STACKTRACE_SUPPORT enabled. They should be selected, but configs
    can always get screwed up.

    -- Steve




    \
     
     \ /
      Last update: 2012-04-18 22:37    [W:0.024 / U:0.368 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site