1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
|
2 <html> |
|
3 <head> |
|
4 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /> |
|
5 <meta http-equiv="Content-Style-Type" content="text/css" /> |
|
6 <meta name="LASTUPDATED" content="06/17/05 11:09:43" /> |
|
7 <title>Stepping Into a Routine</title> |
|
8 <link rel="StyleSheet" href="../../../book.css" type="text/css"/> |
|
9 </head> |
|
10 <body bgcolor="#FFFFFF"> |
|
11 <h2>Stepping Into a Routine</h2> |
|
12 <p>Use the <b>Step Into</b> command (<img src="../../images/icons/btn_stepinto.png" width="18" height="14" />) to execute one source-code statement at a time and follow execution into a routine call.</p> |
|
13 <p>When stepping through a program in a debug session the IDE attempts to match the program counter (PC) location in the executable with a known project source file. If there is no source file associated with the PC the debugger displays in the Debug view the current PC address of the thread (e.g. <span class="code">0x6002CC11(EUSER.DLL)()</span>) instead of the function name. At this point you can open the Disassembly view to step through the assembler code. This most commonly happens when trying to step into Symbian OS code. We recommend that you <a href="work_debug_act_stepover.htm">Step Return</a> out of the OS code and back into your project to continue debugging.<br /> |
|
14 </p> |
|
15 <div class="step"> |
|
16 <h4>Stepping Into a Routine </h4> |
|
17 <ul> |
|
18 <li>Click the Step Into button (<img src="../../images/icons/btn_stepinto.png" width="18" height="14" />) in the <a href="../../reference/view_debug.htm">Debug</a> view </li> |
|
19 </ul> |
|
20 <blockquote> |
|
21 <p>or</p> |
|
22 </blockquote> |
|
23 <ul> |
|
24 <li>Right-click the thread in the Debug view and select Step Into from the Debug contextual menu</li> |
|
25 <p>or</p> |
|
26 <li>Select Run > Step Into from the menu bar </li> |
|
27 <p>After the debugger executes the source-code statement, the current-statement arrow moves to the next statement determined by these rules:</p> |
|
28 <ul> |
|
29 <li>If the executed statement did not call a routine, the current-statement arrow moves to the next statement in the source code.</li> |
|
30 <li>If the executed statement called a routine, the current-statement arrow moves to the first statement in the called routine.</li> |
|
31 <li>If the executed statement is the last statement in a called routine, the current-statement arrow moves to the statement that follows the calling routine.</li> |
|
32 </ul> |
|
33 </ul> |
|
34 </div> |
|
35 <p>For more information on debugging, see <b>C/C++ Development User Guide > Tasks > Running and debugging projects > Debugging</b>.</p> |
|
36 <h5>Related references</h5> |
|
37 <ul> |
|
38 <li><a href="../../concepts/working_with_debugger.htm">Working with the Debugger </a></li> |
|
39 <li><a href="../../reference/view_debug.htm">Debug View</a></li> |
|
40 </ul> |
|
41 <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> |
|
42 |
|
43 </body> |
|
44 </html> |
|