20 <li>identify and correct any path issues with missing source files (shown in gray text). Double-click the missing source file to open a <b>Locate File</b> editor view which enables you to find the missing file. </li> |
20 <li>identify and correct any path issues with missing source files (shown in gray text). Double-click the missing source file to open a <b>Locate File</b> editor view which enables you to find the missing file. </li> |
21 <li>view routines and header files used by the source file. Click the tree control to expand or collapse a list of included header files and routine names for fast navigation. </li> |
21 <li>view routines and header files used by the source file. Click the tree control to expand or collapse a list of included header files and routine names for fast navigation. </li> |
22 <li>find and set breakpoints, watchpoints, and eventpoints in source files. Double-click a source file to open it in an editor view and to review the status of its breakpoints. </li> |
22 <li>find and set breakpoints, watchpoints, and eventpoints in source files. Double-click a source file to open it in an editor view and to review the status of its breakpoints. </li> |
23 </ul> |
23 </ul> |
24 <p>In addition, an <b>Executables</b> project is created in the <a href="view_cpp_projects.htm">Project Explorer</a> view. The binaries shown in the Executables project can be deleted which also removes them from the Executables view. For binaries outside the workspace you must import them into the Executables view so their symbolics can be used during the debug session. <span class="note">You can also drag and drop executables into the view. </span></p> |
24 <p>In addition, an <b>Executables</b> project is created in the <a href="view_cpp_projects.htm">Project Explorer</a> view. The binaries shown in the Executables project can be deleted which also removes them from the Executables view. For binaries outside the workspace you must import them into the Executables view so their symbolics can be used during the debug session. <span class="note">You can also drag and drop executables into the view. </span></p> |
25 <p class="note"><b>NOTE</b> To debug ROM DLLs with System TRK or in stop mode, always specify the <a href="launch_configs/sys_trk_rom_log.htm">ROM Log file</a> in the project's launch configuration. </p> |
25 <p class="note"><b>NOTE</b> To debug ROM DLLs with System TRK or in stop mode, always specify the <a href="../projects/launch/page_rom_log.htm">ROM Log file</a> in the project's launch configuration. </p> |
26 <p align="center"><img src="images/view_executables.png" width="813" height="309" /></p> |
26 <p align="center"><img src="images/view_executables.png" width="813" height="309" /></p> |
27 <p class="figure">Figure 1 - Executables view</p> |
27 <p class="figure">Figure 1 - Executables view</p> |
28 <p align="left">The Executables view consists of the Executable Name and Source File Name panes describled in the table below. Use the Columns button in the toolbar to show or hide specific columns in each pane. Columns can be sorted and rearranged in the order desired. </p> |
28 <p align="left">The Executables view consists of the Executable Name and Source File Name panes describled in the table below. Use the Columns button in the toolbar to show or hide specific columns in each pane. Columns can be sorted and rearranged in the order desired. </p> |
29 <h5>Table 1. Executables view information </h5> |
29 <h5>Table 1. Executables view information </h5> |
30 <table width="88%" border="0" cellpadding="2" cellspacing="0"> |
30 <table width="88%" border="0" cellpadding="2" cellspacing="0"> |