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

Add "text kernel dumps" idea to the ideas page. This might make an

Browse source 
interesting SoC project.
This commit is contained in:
Robert Watson 2007-03-10 00:36:33 +00:00
parent 860f706ccf
commit 6c17a9e275
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=29741
1 changed files with 27 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
en/projects/ideas/index.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/projects/ideas/index.sgml,v 1.93 2007/02/26 17:32:53 joel Exp $">
<!ENTITY date "$FreeBSD: www/en/projects/ideas/index.sgml,v 1.94 2007/03/09 08:30:35 cperciva Exp $">
<!ENTITY title "FreeBSD list of projects and ideas for volunteers">
<!ENTITY % navinclude.developers "INCLUDE">
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -79,6 +79,7 @@
<li><a href="#p-suspend">Suspend to disk</a></li>
<li><a href="#p-bootcode">Sync FreeBSD i386 boot code with DragonFly</a></li>
<li><a href="#p-sysmod">Syscons modularization</a></li>
<li><a href="#p-textdumps">Text kernel dumps</a></li>
</ul>
<h3>Networking</h3>
@ -656,6 +657,31 @@
<hr>
<a name="p-textdumps"></a>
<h2>Text kernel dumps</h2>
<p><strong>Technical Contact</strong>: <a
href="mailto:rwatson@FreeBSD.org">&a.rwatson;</a></p>
<p>While minidumps have dramatically reduced the size of kernel dumps,
limiting dump data to specific regions of kernel memory, kernel dumps are
still very large, and rely on the availability of synchronized source code
and debug symbols. This idea proposes adding a third dump method, the text
dump, which saves the text output from a DDB script into the dump area,
which will be extracted and saved as a text crash log automatically in
production environments.</p>
<p>This would require adding a DDB scripting mechanism and teaching DDB how
to send debug output to a buffer and write it to disk, as well as teaching
savecore how to extract these dumps and save them in an appropriate place.
Possible commands to run in the DDB script might include process and thread
listings, stack traces of kernel threads, lock information, etc, which could
be used without kernel symbols to analyze the failure mode.</p>
<p><strong>Requirements</strong>:</p>
<ul>
<li>Familiarity with FreeBSD kernel debugging environment.</li>
<li>Ability to write C code.</li>
</ul>
<hr>
<!------------------------------------------------------------------>
<!- Networking ->
<!------------------------------------------------------------------>