public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	mingo@elte.hu, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: lib: turn CONFIG_STACKTRACE into an actual option.
Date: Wed, 13 Aug 2014 17:57:12 +0200	[thread overview]
Message-ID: <20140813155712.GA24282@gmail.com> (raw)
In-Reply-To: <20140813150357.GA12025@redhat.com>


* Dave Jones <davej@redhat.com> wrote:

> I was puzzled why /proc/$$/stack had disappeared, until I figured out
> I had disabled the last debug option that did a 'select STACKTRACE'.
> This patch makes the option show up at config time, so it can be
> enabled without enabling any of the more heavyweight debug options.
> 
> Signed-off-by: Dave Jones <davej@redhat.com>
> 
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index 7a638aa3545b..96c64beac12a 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1008,8 +1008,13 @@ config TRACE_IRQFLAGS
>  	  either tracing or lock debugging.
>  
>  config STACKTRACE
> -	bool
> +	bool "Stack backtrace support"
>  	depends on STACKTRACE_SUPPORT
> +	help
> +	  This option causes the kernel to create a /proc/pid/stack for
> +	  every process, showing its current stack trace.
> +	  It is also used by various kernel debugging features that require
> +	  stack trace generation.
>  
>  config DEBUG_KOBJECT
>  	bool "kobject debugging"

Acked-by: Ingo Molnar <mingo@kernel.org>

Thanks,

	Ingo

      reply	other threads:[~2014-08-13 15:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 19:24 lib: turn CONFIG_STACKTRACE into an actual option Dave Jones
2014-08-13 15:03 ` Dave Jones
2014-08-13 15:57   ` Ingo Molnar [this message]

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=20140813155712.GA24282@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox