debuggercdi/com.nokia.carbide.cpp.debug.crashdebugger/html/crash_launch_config.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 XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<link href="../book.css" rel="stylesheet" type="text/css" />
<title>Crash Debugger Launch Configuration</title>
</head>
<body bgcolor="#FFFFFF">
<h2>Symbian OS Crash Debugger Launch Configuration</h2>
<p>Use the Run or Debug window to define a launch configuration for the crash debugger. Select <b>Run > Open Run Dialog...</b> to open the Run window. Select <b>Run > Open Debug Dialog...</b> to open the Debug window (Figure 1). Select Symbian OS Crash Debugger and click the New launch configuration icon. In the Name field enter a unique name for your launch configuration. Specify your connection information and select the ROM Log tab (figure 2).</p>
<p class="figure"><img src="DebuggingInformation/crash_debug_connection.png" width="705" height="451" /></p>
<p class="figure">Figure 1 - Connection Tab </p>
<p>In the ROM Log pane specify a ROM log file that was generated when building the rom image. The ROM log file is necessary for finding out the address for each module in the rom log file. Specify the Symbian OS kit Epoc32 directory to resolve the full paths for the various modules in the rom log file. By specifying the rom log file and epoc32 path you will be able to view source code (figure 3) for the crash debug session.</p>
<p align="center"><img src="DebuggingInformation/crash_debug_romlog.png" width="705" height="451" /></p>
<p class="figure">Figure 2 - ROM Log Tab</p>
<p align="center" class="figure"><img src="DebuggingInformation/crash_debug_source.png" width="1024" height="591" /></p>
<p class="figure">Figure 3 - Crash Debug Source Code </p>
<h5>Related concepts</h5>
<ul>
<li><a href="DebuggingInformation/CrashDebuggerUsingCommandSyntax.guide.html">Debug Monitor</a></li>
</ul>
<h5 align="left">Related references</h5>
<ul>
<li><a href="DebuggingInformation/CrashDebugger_cmd.guide.html">Crash Debugger Commands</a></li>
<li><a href="DebuggingInformation/index.html">Symbian OS Debugging Information</a></li>
</ul>
<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>