From d5140b068dfd31c2b4d5c34e1c51f5267398a610 Mon Sep 17 00:00:00 2001 From: Joel Dahl Date: Fri, 16 Jun 2006 20:47:14 +0000 Subject: [PATCH] Improve wording and grammar. Reviewed by: brd --- .../kerneldebug/chapter.sgml | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml b/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml index 80699108bd..d3ce85d834 100644 --- a/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml +++ b/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml @@ -823,18 +823,18 @@ Reading symbols from /sys/modules/linux/linux.ko...done. - Debugging the Deadlocks + Debugging Deadlocks You may experience so called deadlocks, the situation where - system stops doing useful work. To provide the helpful bug report - in this situation, you shall use ddb as described above. Please, - include the output of ps and + a system stops doing useful work. To provide a helpful bug report + in this situation, use &man.ddb.4; as described above. + Include the output of ps and trace for suspected processes in the report. - If possible, consider doing further investigation. Receipt - below is especially useful if you suspect deadlock occurs in the - VFS layer. Add the options + If possible, consider doing further investigation. The receipt + below is especially useful if you suspect that a deadlock occurs in the + VFS layer. Add the following options makeoptions DEBUG=-g options INVARIANTS options INVARIANT_SUPPORT @@ -843,15 +843,15 @@ Reading symbols from /sys/modules/linux/linux.ko...done. options DEBUG_VFS_LOCKS options DIAGNOSTIC - to the kernel config. When deadlock occurs, in addition to the + to the kernel configuration file. When a deadlock occurs, in addition to the output of the ps command, provide information from the show allpcpu, show alllocks, show lockedvnods and show alltrace. - For threaded processes, to obtain meaningful backtraces, use + To obtain meaningful backtraces for threaded processes, use thread thread-id to switch to the thread - stack, and do backtrace with where. + stack, and do a backtrace with where.