<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
<title>Debug view</title>
<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
</head>
<body >
<h2>Debug view </h2>
<p>The <b>Debug</b> view provides an overview of the debug session as it relates to the executing program. The target debugging information is shown in a tree hierarchy. The items that appear there include:</p>
<ul>
<li>Launch instance (<img src="../images/debug_launch_instance_icon.png" width="16" height="16" align="absmiddle" />) - launch configuration name and type </li>
<li>Debugger instance (<img src="../images/debug_debugger_instance_icon.png" width="18" height="16" align="absmiddle" />) - debugger name and state </li>
<li>Executable instances (<img src="../images/debug_codebug_instance_icon.png" width="17" height="17" align="absmiddle" />) - other executables called by the launch instance </li>
<li>Thread instance (<img src="../images/debug_thread_instance_icon.png" width="16" height="15" align="absmiddle" />) - thread number and state </li>
<li>Stack frame reference (<img src="../images/debug_stack_frame_instance_icon.png" width="16" height="14" align="absmiddle" />) - displays stack frame number, function, filename, and file line number when symbols are available and stack frame number, memory address, and filename when symbols are not available </li>
</ul>
<p class="note"><b>NOTE</b> The number beside the thread label is a reference counter, not a thread
identification number (TID).</p>
<p>The CDT displays stack frames as child elements. It displays the reason for the suspension beside the thread, (such as end of stepping range, breakpoint hit, and signal received). When a program exits, the exit code is displayed.</p>
<p>In addition to controlling the individual stepping of your programs, you can also control the debug session. You can perform actions such as terminating the session and stopping the program by using the debug launch controls available from Debug view. See Table 1 for details. </p>
<p>Figure 1 shows the Debug view. Table 1 explains the items in the view.</p>
<p align="center"><img src="../images/view_debug.png" width="545" height="264" /></p>
<p class="figure">Figure 1 - Debug view</p>
<h5>Table 1 Debug view—items</h5>
<table width="100%" border="0" cellpadding="2" cellspacing="0">
<tr>
<th width="29%" scope="col">Item</th>
<th width="14%" scope="col">Icon</th>
<th width="57%" scope="col">Explanation</th>
</tr>
<tr>
<td><a href="cmds_resuming.htm">Resume</a></td>
<td><div align="center"><img src="../images/icon_debug_resume_btn.png" width="19" height="16" /></div></td>
<td><p>Click to perform these tasks:</p>
<ul>
<li>Continue execution up to the next breakpoint, watchpoint, or eventpoint</li>
<li>Run the program until it exits</li>
<li>Continue execution of a currently stopped program</li>
</ul></td>
</tr>
<tr>
<td><a href="cmds_resuming.htm">Suspend</a></td>
<td><div align="center"><img src="../images/icon_debug_suspend_btn.png" width="19" height="16" /></div></td>
<td>Click to stop (pause) program execution.</td>
</tr>
<tr>
<td><a href="cmds_starting.htm">Terminate</a></td>
<td><div align="center"><img src="../images/icon_debug_terminate_btn.png" width="17" height="17" /></div></td>
<td>Click to terminate program execution. This ends the debugging session.</td>
</tr>
<tr>
<td><a href="cmds_other.htm">Disconnect</a></td>
<td><center>
<img src="../images/icon_debug_disconnect.png" width="20" height="21">
</center>
</td>
<td><p>Detaches the debugger from the selected process (useful for debugging attached processes).</p>
<p class="note"><b>NOTE</b> After detaching the debugger from an on-device process, closing CODA on the device will also close the process. </p></td>
</tr>
<tr>
<td><a href="cmds_other.htm">Remove All Terminated</a> </td>
<td><center>
<img src="../images/icon_debug_remove_all.png" width="21" height="19">
</center>
</td>
<td>Clears all terminated processes in Debug view.</td>
</tr>
<tr>
<td><a href="cmds_starting.htm">Restart</a></td>
<td><div align="center"><img src="../images/icon_debug_restart_btn.png" width="19" height="19" /></div></td>
<td>Returns the debugger to the beginning of the program and begins execution again. This behavior is equivalent to killing execution, then starting a new debugging session.</td>
</tr>
<tr>
<td><a href="cmds_stepping.htm">Step Over</a></td>
<td><div align="center"><img src="../images/icon_debug_step_over_btn.png" width="18" height="14" /></div></td>
<td>Click to execute the current line, including any routines, and proceed to the next statement.</td>
</tr>
<tr>
<td><a href="cmds_stepping.htm">Step Into</a></td>
<td><div align="center"><img src="../images/icon_debug_step_into_btn.png" width="18" height="14" /></div></td>
<td>Click to execute the current line, following execution inside a routine.</td>
</tr>
<tr>
<td><a href="cmds_stepping.htm">Step Return</a></td>
<td><div align="center"><img src="../images/icon_debug_step_return_btn.png" width="18" height="15" /></div></td>
<td>Click to continue execution to the end of the current routine, then follow execution to the routine’s caller.</td>
</tr>
<tr>
<td><a href="cmds_other.htm">Instruction Stepping Mode </a></td>
<td><div align="center"><img src="../images/icon_debug_instr_stepping_mode.png" width="18" height="16"></div></td>
<td>Activate to enable instruction stepping mode to examine a program as it steps into disassembled code.</td>
</tr>
</table>
<h4>Other references</h4>
<ul>
<li><a href="debug.htm">Debugging overview</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>