debuggercdi/com.nokia.carbide.cpp.debug.crashdebugger/html/DebuggingInformation/CrashDebuggerFindingFault.guide.html
Overhaul of RCOMP/GCCE error parsing to fix 8901:
-RCOMP error parser will defer C preprocessor errors to GCCECompiler error parser.
-GCCE error parser is splited into compiler/assembler/linker, calling their counterpart in CDT respectively before handling special cases.
-Updated error messages RCOMP error parser according to latest copy of RCOMP source.
-WINSCW build configuration is using CDT GCC error parser instead of GCCE(for RCOMP C preprocessor error)
Updated test case for error parsing
-Added Bugzilla regression for GCC and make error parser
-Converted test case from hardcoded SDK_ID to picking up the first SDK from device.xml with the build config specified by the test.
-Fixed bug in test harness for input file ends on the last line so it was processed in the same run.
-Fixed bug in test harness for not clearing problem view before each run(for visual cross check).
-Rewritten test harness to use JDOM XML handling(from JAXP), to solve deployment issue in newer JRE.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html><head>
<title>Finding the type of fault in Debugging information</title>
<link href="sysdoc-eclipse.css" type="text/css" rel="stylesheet" media="screen">
<link href="sysdoc-eclipse.css" type="text/css" rel="stylesheet" media="print">
<link href="../../book.css" type="text/css" rel="stylesheet" >
<div class="Head1">
<h2>Finding the Type of Fault</h2>
</div><div>
<p>The type of fault is the first piece of information that you need.
There are two possibilities:</p>
<ul>
<li>
<p><a href="CrashDebuggerFindingFault.guide02.html" title="Finding the type of fault / Unhandled exceptions">an unhandled exception has occurred</a></p>
</li>
<li>
<p><a href="CrashDebuggerFindingFault.guide03.html" title="Finding the type of fault / Panics">a panic has occurred</a></p>
</li>
</ul>
<p>To start, use the
<a href="CrashDebugger_cmd_f.guide.html" title="The debug monitor and command syntax / f - display kernel fault information">f</a> command. You
will see something like this: </p>
<p class="listing">Fault Category: Exception Fault Reason: 10000000<br>
ExcId 00000001 CodeAddr f800415c DataAddr 00000000 Extra 00000005<br>Exc 1 Cpsr=60000013 FAR=00000000 FSR=00000005<br>
R0=64007328 R1=00000000 R2=00000000 R3=00000001<br>
R4=64007328 R5=640074c0 R6=00000000 R7=f8047ba4<br>
R8=64006f80 R9=64006fec R10=00000013 R11=64006ec4<br>
R12=00000001 R13=000029b4 R14=0000016c R15=f800415c<br>R13Svc=64006ea8 R14Svc=f8002b2c SpsrSvc=600000ff</p>
<p>The <em>Fault Category</em> field shows the type of fault, in
this case an exception.</p>
</div><div class="Head2"></div><div></div>
<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
</body>
</html>