diff -r bf9a2104bee6 -r 5d016a880824 debuggercdi/com.nokia.carbide.cpp.debug.crashdebugger/html/DebuggingInformation/CrashDebuggerFindingFault.guide03.html --- a/debuggercdi/com.nokia.carbide.cpp.debug.crashdebugger/html/DebuggingInformation/CrashDebuggerFindingFault.guide03.html Thu Feb 18 14:39:30 2010 -0600 +++ b/debuggercdi/com.nokia.carbide.cpp.debug.crashdebugger/html/DebuggingInformation/CrashDebuggerFindingFault.guide03.html Thu Feb 18 15:11:20 2010 -0600 @@ -1,32 +1,32 @@ - -
-If the Fault Category is not Exception, -then the fault is due to a panic. In this case the only other valid field is -the Fault reason; the values of all other fields are -meaningless.
-The panic number is the low 16-bits of the fault reason, shown in -hexadecimal.
-For example, a KERN 27 panic would generate:
-Fault Category: KERN Fault Reason: 0000001b
- ExcId ffffee5e CodeAddr ffff99a9 DataAddr bfff3e54 Extra fffec4cd
If the panic is KERN 4, then a thread or process marked as -protected has panicked. For other panics, kernel side code has panicked; this -code is either in the kernel itself or in a device driver.
-See Extracting information about the kernel to find out which process and thread were -running at the time of the panic.
- -If the Fault Category is not Exception, +then the fault is due to a panic. In this case the only other valid field is +the Fault reason; the values of all other fields are +meaningless.
+The panic number is the low 16-bits of the fault reason, shown in +hexadecimal.
+For example, a KERN 27 panic would generate:
+Fault Category: KERN Fault Reason: 0000001b
+ ExcId ffffee5e CodeAddr ffff99a9 DataAddr bfff3e54 Extra fffec4cd
If the panic is KERN 4, then a thread or process marked as +protected has panicked. For other panics, kernel side code has panicked; this +code is either in the kernel itself or in a device driver.
+See Extracting information about the kernel to find out which process and thread were +running at the time of the panic.
+ +