From: Dave Jones <davej@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Eric Sandeen <sandeen@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] more helpful WARN_ON and BUG_ON messages
Date: Fri, 20 Oct 2006 22:41:05 -0400 [thread overview]
Message-ID: <20061021024105.GA17706@redhat.com> (raw)
In-Reply-To: <20061020220717.GY3502@stusta.de>
On Sat, Oct 21, 2006 at 12:07:17AM +0200, Adrian Bunk wrote:
> > Most debugging code makes the kernel bigger, slower... and easier to
> > debug, no?
> >
> > It's not a question of not being -able- to locate sources; it's a
> > question of being able to look at a bug report and triage it quickly
> > without digging around to find the kernel du jour that produced it. *shrug*
>
> It's not that BUGs were that frequent.
You're not trying hard enough ;)
> And with your suggestion "I suppose this could be put under CONFIG_DEBUG",
> it would anyway be turned off by nearly everyone.
For better bug reports, 16K is peanuts. We had exactly the same straw-man
come up when kksymoops was first proposed. And now, most people don't run
without it.
I've seen numerous cases where reporters have hand transcribed BUG() reports,
and got the line numbers wrong because they misremembered a 4 digit number.
Words are inherently easier to remember, and even if typoed, usually there's
enough context to figure out what the problem was without another round-trip
to the bug reporter.
If this were optional, I don't see how anyone can argue against it,
and that should be a trivial improvement to Eric's existing patch.
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2006-10-21 2:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 16:23 [PATCH] more helpful WARN_ON and BUG_ON messages Eric Sandeen
2006-10-20 16:54 ` [PATCH] (update) " Eric Sandeen
2006-10-20 17:02 ` Peter Zijlstra
2006-10-20 19:30 ` Eric Sandeen
2006-10-20 21:16 ` [PATCH] " Jeremy Fitzhardinge
2006-10-23 3:18 ` Eric Sandeen
2006-10-20 21:41 ` Adrian Bunk
2006-10-20 21:56 ` Eric Sandeen
2006-10-20 22:07 ` Adrian Bunk
2006-10-21 2:41 ` Dave Jones [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=20061021024105.GA17706@redhat.com \
--to=davej@redhat.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.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