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"></link>
<title>Memory Dump Options</title>
</head>
<body bgcolor="#FFFFFF">
<h2>Memory Dump Options </h2>
<p>Use the <b>Memory Dump Options </b> window to specify the starting address and length of memory data to display in the <b>Crash Debugger Console</b> view.</p>
<p align="center"><img src="DebuggingInformation/wnd_memory_dump.png" width="430" height="170" /></p>
<p align="center" class="figure">Figure 1 - Memory Dump Options window</p>
<div class="step">
<h4 align="left">Displaying Memory Data </h4>
<ol>
<li>Enter a memory dump command or right-click in the Crash Debugger Console view and select a memory dump command</li>
<p>The <b>Memory Dump Options</b> window appears.</p>
<li>Enter the starting address in hexadecimal into the Address text box </li>
<li>Enter the length of the memory space to display into the Length (Hexadecimal) text box </li>
<li>Click OK </li>
<p>The <b>Memory Dump Options</b> window closes and the specified memory data appears in the <b>Crash Debugger Console</b> view.</p>
</ol>
</div>
<h5>Related concepts</h5>
<ul>
<li><a href="DebuggingInformation/CrashDebuggerUsingCommandSyntax.guide.html">Debug Monitor</a></li>
<li><a href="DebuggingInformation/index.html">Symbian OS Debugging Information</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/CrashDebuggerExaminingMemory.guide.html">Examining Memory</a></li>
<li><a href="DebuggingInformation/CrashDebuggerExaminingMemory.guide02.html">Dumping the Contents of Classes</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>