From: "Daniel Bonekeeper" <thehazard@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Automatic Kernel Bug Report
Date: Sun, 9 Jul 2006 04:45:14 -0400 [thread overview]
Message-ID: <e1e1d5f40607090145k365c0009ia3448d71290154c@mail.gmail.com> (raw)
Well this probably was already discussed. Some distros have automatic
bug reporting tools that are triggered when something bad happens
(don't know if includes kernel stuff). But have anybody thought about
some kind of bug report tool that, under an Oops like a NULL point
dereference, it creates for example a packed file with the config used
to build the kernel, the kernel version, loaded modules, some hardware
info, backtraces, everything that could be useful for debugging, and
sends to a server to be catalogued ?
I know for sure that a lot of people don't use to send bug reports,
either because they are in a hurry and forget, or because they just
don't know how or that it even exists. We could have something that,
under certain bad events, sends that info to a userspace program and
lets it handle that bug report problem automatically (here distros can
be creative).
I'm not sure about including this on distro's kernels, since they
already use some kind of bug report mechanism, and usually distro
kernels are very different from the vanilla one, which could make it
harder to debug the problem. So, distros should ship their kernels
with this thing disabled (or enabled, but having the handler on
userspace pointing to them, and not for us).
Wouldn't that be helpful ?
Daniel
--
What this world needs is a good five-dollar plasma weapon.
next reply other threads:[~2006-07-09 8:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 8:45 Daniel Bonekeeper [this message]
2006-07-09 9:45 ` Michal Piotrowski
2006-07-09 10:29 ` Daniel Bonekeeper
2006-07-09 12:58 ` Adrian Bunk
2006-07-09 18:46 ` Daniel Bonekeeper
2006-07-09 19:11 ` Adrian Bunk
2006-07-09 20:01 ` Daniel Bonekeeper
2006-07-09 20:19 ` Valdis.Kletnieks
2006-07-09 20:27 ` Daniel Bonekeeper
2006-07-10 8:11 ` Pavel Machek
2006-07-10 17:40 ` Daniel Bonekeeper
2006-07-10 17:59 ` Valdis.Kletnieks
2006-07-10 22:05 ` Daniel Bonekeeper
2006-07-10 23:41 ` Lee Revell
2006-07-11 1:15 ` Daniel Bonekeeper
2006-07-10 18:41 ` Horst von Brand
2006-07-10 21:34 ` Daniel Bonekeeper
2006-07-11 14:16 ` Horst von Brand
2006-07-09 20:24 ` Diego Calleja
2006-07-09 20:37 ` Daniel Bonekeeper
2006-07-09 22:19 ` Diego Calleja
2006-07-09 22:49 ` Daniel Bonekeeper
2006-07-09 20:25 ` Jesper Juhl
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=e1e1d5f40607090145k365c0009ia3448d71290154c@mail.gmail.com \
--to=thehazard@gmail.com \
--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
all inboxes | Powered by JetHome®