Messages in this thread | | | Date | Tue, 17 Apr 2012 23:50:04 -0400 | From | Dave Jones <> | Subject | Re: [3.4-rc3] Thread overran stack, or stack corrupted |
| |
On Tue, Apr 17, 2012 at 11:43:31PM -0400, Steven Rostedt wrote: > On Tue, 2012-04-17 at 23:15 -0400, Dave Jones wrote: > > > That looks handy. Doesn't seem to work for me though on my test box. > > (config option is enabled.) > > > > # echo 1 > /proc/sys/kernel/stack_tracer_enabled > > # cat /sys/kernel/debug/tracing/stack_trace > > Depth Size Location (-1 entries) > > ----- ---- -------- > > > > That's all she wrote. > > Hmm, was there any problems with the function tracer? > Messages in dmesg?
nope.
> Just to make sure, what does > > /sys/kernel/debug/tracing/enabled_functions > > have?
33503 lines.
> 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.
Dave
| |