os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

New SoC idea: automated kernel crash reporting.

Browse source
This commit is contained in:
Xin LI 2007-03-17 08:48:46 +00:00
parent 7c83c5a677
commit f342206988
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=29808
1 changed files with 35 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

36
en/projects/ideas/ideas.xml
View file

@ -15,7 +15,7 @@ Ideas//EN"
<ideas>
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd">
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.11 2007/03/16 16:49:17 murray Exp $
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.12 2007/03/16 17:59:05 dds Exp $
</cvs:keyword>
</cvs:keywords>
@ -121,6 +121,40 @@ Ideas//EN"
<category>
<title>Kernel</title>
<idea id="autoreport" class="soc">
<title>Automated kernel crash reporting system</title>
<desc>
<p><strong>Technical contact</strong>: <a href="mailto:delphij@FreeBSD.org">Xin LI</a>, <a
href="mailto:howard0su@gmail.com">Howard SU</a></p>
<p>In some recent operating systems, it is common that crashes are
automatically reported to its vendor, which is very helpful for
finding hidden problems that can not be easily triggered by usual
test cases. Newer GNOME applications also has similar functionalities.</p>
<p>This project would consist two parts. One is some improvements over
the current savecore rc.d script to teach it how to collect necessary
information (of course, automatic reporting has to be explicitly enabled
by individual system administrators, and should have at least three
options: not to send out anything at all as a default, send out after
administrator confirmation, and automatically send all necessary information)</p>
<p>Another part is the server side one, which will keep a database of backtraces
where similar (call stack minus addresses) reports are kept together and be
considered as a "vote", to make it possible for developers and release engineers
to focus on the most commonly triggered issues.</p>
<p><strong>Requirements</strong>:</p>
<ul>
<li>Strong knowledge of C.</li>
<li>Understanding of kernel debugging.</li>
<li>Knowledge about web application as well as database.</li>
<li>Understanding of user privacy protection.</li>
</ul>
</desc>
</idea>
<idea id="setproctitle" class="soc">
<title>Avoiding syscall overhead</title>