From: Eric Sandeen <sandeen@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: 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 16:56:37 -0500 [thread overview]
Message-ID: <45394615.5050406@redhat.com> (raw)
In-Reply-To: <20061020214101.GX3502@stusta.de>
Adrian Bunk wrote:
> Who really needs this considering it implies a size increase of the
> kernel image?
>
> Using a kernel tree so unusual that you can't locate the source anymore
> sounds like an extremely rare and unintelligent situation, not something
> that must be handled.
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*
-Eric
next prev parent reply other threads:[~2006-10-20 21:57 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 [this message]
2006-10-20 22:07 ` Adrian Bunk
2006-10-21 2:41 ` Dave Jones
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=45394615.5050406@redhat.com \
--to=sandeen@redhat.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.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.