From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Grant Likely" <grant.likely@secretlab.ca>
Cc: Scott Wood <scottwood@freescale.com>, ppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: verbose kernel debug
Date: Tue, 29 Jul 2008 20:17:49 -0400 [thread overview]
Message-ID: <9e4733910807291717g7096b8eas455964e0bbb637b9@mail.gmail.com> (raw)
In-Reply-To: <9e4733910807291709j49cacaa7gcc05f075f0691682@mail.gmail.com>
Why isn't PowerPC in the depends on?
config DEBUG_BUGVERBOSE
bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EMBEDDED
depends on BUG
depends on ARM || AVR32 || M32R || M68K || SPARC32 || SPARC64 || \
FRV || SUPERH || GENERIC_BUG || BLACKFIN || MN10300
default !EMBEDDED
help
Say Y here to make BUG() panics output the file name and line number
of the BUG call as well as the EIP and oops trace. This aids
debugging but costs about 70-100K of memory.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2008-07-30 0:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 22:47 verbose kernel debug Jon Smirl
2008-07-29 23:05 ` Scott Wood
2008-07-29 23:12 ` Jon Smirl
2008-07-29 23:40 ` Grant Likely
2008-07-30 0:09 ` Jon Smirl
2008-07-30 0:17 ` Jon Smirl [this message]
2008-07-30 0:28 ` Jon Smirl
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=9e4733910807291717g7096b8eas455964e0bbb637b9@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=Linuxppc-dev@ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=scottwood@freescale.com \
/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;
as well as URLs for NNTP newsgroup(s).