All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [3.4-rc3] Thread overran stack, or stack corrupted
Date: Tue, 17 Apr 2012 23:50:04 -0400	[thread overview]
Message-ID: <20120418035004.GA31465@redhat.com> (raw)
In-Reply-To: <1334720611.28106.25.camel@gandalf.stny.rr.com>

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

  reply	other threads:[~2012-04-18  3:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17 17:21 [3.4-rc3] Thread overran stack, or stack corrupted Dave Jones
2012-04-17 20:20 ` Linus Torvalds
2012-04-17 20:32   ` Dave Jones
2012-04-18  1:36     ` Linus Torvalds
2012-04-18  2:27       ` Steven Rostedt
2012-04-18  3:15         ` Dave Jones
2012-04-18  3:43           ` Steven Rostedt
2012-04-18  3:50             ` Dave Jones [this message]
2012-04-18  3:57               ` Steven Rostedt
2012-04-18  4:00                 ` Steven Rostedt
2012-04-18  4:07                   ` Dave Jones
2012-04-18  4:06                 ` Dave Jones
2012-04-18  4:09                   ` Steven Rostedt
2012-04-18 13:58                     ` Dave Jones
2012-04-18 14:56                       ` Steven Rostedt
2012-04-18 15:27                         ` Dave Jones
2012-04-18 15:30                         ` Dave Jones
2012-04-18 16:43                           ` Steven Rostedt
2012-05-23 14:37                             ` Steven Rostedt
2012-05-23 15:05                               ` Dave Jones
2012-05-23 15:14                                 ` Steven Rostedt
2012-04-18 15:40                         ` Steven Rostedt
2012-04-18  3:19       ` Dave Jones
2012-04-18 17:02         ` Linus Torvalds
2012-04-18 17:14           ` Dave Jones
2012-04-18 18:24             ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120418035004.GA31465@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.