2 <html> |
2 <html> |
3 <head> |
3 <head> |
4 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /> |
4 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /> |
5 <meta http-equiv="Content-Style-Type" content="text/css" /> |
5 <meta http-equiv="Content-Style-Type" content="text/css" /> |
6 <meta name="LASTUPDATED" content="06/17/05 11:09:43" /> |
6 <meta name="LASTUPDATED" content="06/17/05 11:09:43" /> |
|
7 <script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script> |
7 <title>Debug view</title> |
8 <title>Debug view</title> |
8 <link rel="StyleSheet" href="../../../book.css" type="text/css"/> |
9 <link rel="StyleSheet" href="../../../book.css" type="text/css"/> |
9 </head> |
10 </head> |
10 <body > |
11 <body > |
11 <h2>Debug view </h2> |
12 <h2>Debug view </h2> |
12 <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> |
13 <p>The <img src="../../images/command_link.png" border="0" alt="" /> <a href='javascript:executeCommand("org.eclipse.ui.views.showView(org.eclipse.ui.views.showView.viewId=org.eclipse.debug.ui.DebugView)")' class="command-link"><b>Debug</b></a> 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> |
13 <ul> |
14 <ul> |
14 <li>Launch instance (<img src="../images/debug_launch_instance_icon.png" width="16" height="16" align="absmiddle" />) - launch configuration name and type </li> |
15 <li>Launch instance (<img src="../images/debug_launch_instance_icon.png" width="16" height="16" align="absmiddle" />) - launch configuration name and type </li> |
15 <li>Debugger instance (<img src="../images/debug_debugger_instance_icon.png" width="18" height="16" align="absmiddle" />) - debugger name and state </li> |
16 <li>Debugger instance (<img src="../images/debug_debugger_instance_icon.png" width="18" height="16" align="absmiddle" />) - debugger name and state </li> |
16 <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> |
17 <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> |
17 <li>Thread instance (<img src="../images/debug_thread_instance_icon.png" width="16" height="15" align="absmiddle" />) - thread number and state </li> |
18 <li>Thread instance (<img src="../images/debug_thread_instance_icon.png" width="16" height="15" align="absmiddle" />) - thread number and state (Running, Suspended, etc.)</li> |
18 <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> |
19 <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> |
19 </ul> |
20 </ul> |
20 <p class="note"><b>NOTE</b> The number beside the thread label is a reference counter, not a thread |
21 <p class="note"><b>NOTE</b> The number beside the thread label is a reference counter, not a thread |
21 identification number (TID).</p> |
22 identification number (TID).</p> |
22 <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> |
23 <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> |
23 <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> |
24 <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> |
24 <p>Figure 1 shows the Debug view. Table 1 explains the items in the view.</p> |
25 <p>Figure 1 shows the <b>Debug</b> view. Table 1 explains the items in the view.</p> |
25 <p align="center"><img src="../images/view_debug.png" width="545" height="264" /></p> |
26 <p align="center"><img src="../images/view_debug.png" width="545" height="264" /></p> |
26 <p class="figure">Figure 1 - Debug view</p> |
27 <p class="figure">Figure 1 - Debug view</p> |
27 <h5>Table 1 Debug view—items</h5> |
28 <h5>Table 1 Debug view—items</h5> |
28 <table width="100%" border="0" cellpadding="2" cellspacing="0"> |
29 <table width="100%" border="0" cellpadding="2" cellspacing="0"> |
29 <tr> |
30 <tr> |