debuggercdi/com.nokia.carbide.cpp.debug.crashdebugger/html/DebuggingInformation/CrashDebuggerUsingCommandSyntax.guide.html
Catch exceptions thrown by remote connection listener implementations so they don't propagate too high in the call stack.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html><head>
<title>Debug Monitor</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>Debug Monitor</h2>
</div><div>
<p>The debug monitor is entered when the kernel crashes, if a system
process panics, or an unhandled processor exception occurs. Under normal
circumstances this ought not to happen, but when the kernel faults, the device
enters the kernel debug monitor. The Debug Monitor appears in Carbide as a view within the Crash Debugger perspective. Use the <b>Crash Debugger Console</b> view to enter commands and interact with the Debug Monitor on the device. </p>
<p>Notes:</p>
<ul>
<li>
<p>the EKA2 debug monitor is very similar to the EKA1 version,
although the details displayed may be different.</p>
</li>
<li>
<p>you will occasionally find references to the <em>crash
debugger</em>; this is the same as the debug monitor</p>
</li>
</ul>
</div>
<h5>Related tasks</h5>
<ul>
<li><a href="CrashDebugger_Setup.html">Setting Up the Debug Monitor </a></li>
</ul>
<h5>Related references </h5>
<ul>
<li><a href="CrashDebugger_cmd.guide.html">Crash Debugger Commands</a></li>
</ul>
<div id="footer">Copyright © 2010 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>