From: "Philip R. Auld" <prauld@egenera.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Keith Owens <kaos@ocs.com.au>, Jeremy Jackson <jerj@coplanar.net>,
linux-kernel@vger.kernel.org
Subject: Re: [QUESTION] which kernel debugger is "best"?
Date: Mon, 01 Apr 2002 08:44:40 -0500 [thread overview]
Message-ID: <3CA86448.463C0532@egenera.com> (raw)
In-Reply-To: Your message of "Fri, 29 Mar 2002 19:18:39 -0800." <3CA52E8F.C8D0E5F8@zip.com.au> <2178.1017459962@ocs3.intra.ocs.com.au> <3CA53DE5.668AC7AB@zip.com.au>
Andrew Morton wrote:
>
[other stuff cut]
>
> I would like to see kdb shipped in the mainline kernel, so that
> we can get better diagnostic reports from users/testers.
>
Here, Here! That and crash dumps are important to providing
high quality support to enterprise customers.
Phil
--
Philip R. Auld, Ph.D. Technical Staff
Egenera, Inc. pauld@egenera.com
165 Forest St., Marlboro, MA 01752 (508)786-9444
next prev parent reply other threads:[~2002-04-01 13:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-30 2:38 [QUESTION] which kernel debugger is "best"? Jeremy Jackson
2002-03-30 3:18 ` Andrew Morton
2002-03-30 3:46 ` Keith Owens
2002-03-30 4:24 ` Andrew Morton
2002-03-30 4:25 ` David S. Miller
2002-03-30 15:22 ` Peter Wächtler
2002-04-01 9:20 ` Amit S. Kale
2002-04-01 13:44 ` Philip R. Auld [this message]
2002-03-30 4:04 ` Keith Owens
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=3CA86448.463C0532@egenera.com \
--to=prauld@egenera.com \
--cc=akpm@zip.com.au \
--cc=jerj@coplanar.net \
--cc=kaos@ocs.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox