30 <td>AnalyzeTool Engine</td> |
30 <td>AnalyzeTool Engine</td> |
31 <td>AnalyzeTool uses the command line utility <i>atool.exe</i> which is |
31 <td>AnalyzeTool uses the command line utility <i>atool.exe</i> which is |
32 used for instrumenting and uninstrumenting the project and analysing |
32 used for instrumenting and uninstrumenting the project and analysing |
33 captured data. |
33 captured data. |
34 <ul> |
34 <ul> |
35 <li>Use internal engine. This option uses the built-in version of |
35 <li><strong>Use internal command line engine</strong>: This option |
36 <i>atool.exe</i>. </li> |
36 uses the built-in version of <i>atool.exe</i>. </li> |
37 <li>Use external command line engine. This options uses |
37 <li><strong>Use external command line engine</strong>: This options |
38 <i>atool.exe</i> from a user-defined location. |
38 uses <i>atool.exe</i> from the location selected to the |
39 <ul> |
39 <strong>Atool.exe path</strong> field. </li> |
40 </ul> |
|
41 </li> |
|
42 </ul> |
40 </ul> |
|
41 |
|
42 <p>When the <em>atool.exe</em> version has been selected, the system |
|
43 automatically checks that it matches with the version of the |
|
44 AnalyzeTool Carbide extension. In case of a mismatch, an error is |
|
45 displayed "<em>Command Line Engine is older than x.x.x</em>", and the |
|
46 <strong>Apply</strong> and <strong>OK</strong> buttons are disnabled. |
|
47 In this case you need to select a later CLE tool version. For more |
|
48 information, see <a href="../reference/troubleshooting.htm">AnalyzeTool |
|
49 Troubleshooting</a>.</p> |
43 </td> |
50 </td> |
44 </tr> |
51 </tr> |
45 <!--<tr> |
52 <!--<tr> |
46 <td>Generate statistics</td> |
53 <td>Generate statistics</td> |
47 <td>Enables AnalyzeTool to generate memory statistics.</td> |
54 <td>Enables AnalyzeTool to generate memory statistics.</td> |
51 <td>Enables command line engine debug information to the <b>Console</b> |
58 <td>Enables command line engine debug information to the <b>Console</b> |
52 view.</td> |
59 view.</td> |
53 </tr> |
60 </tr> |
54 <tr> |
61 <tr> |
55 <td>Engine version</td> |
62 <td>Engine version</td> |
56 <td>Displays selected engine version number.</td> |
63 <td>Displays selected engine's version number.</td> |
57 </tr> |
64 </tr> |
58 <tr> |
65 <tr> |
59 <td>Data gathering mode</td> |
66 <td>Output mode</td> |
60 <td>Specifies the data gathering mode for AnalyzeTool build. |
67 <td>Specifies the output mode for AnalyzeTool build. |
61 <ul> |
68 <ul> |
62 <li>Monitored External or External: This option will send the memory |
69 <li><strong>Output to trace (recommended)</strong>: This option will |
63 analysis data through tracing utility connection. For more |
70 send the memory analysis data through tracing utility connection. |
64 information, see <a |
71 For more information, see <a |
65 href="../tasks/capture.htm#capture_external">Capturing data in |
72 href="../tasks/capture.htm#capture_external">Capturing data in |
66 external data gathering mode</a>.</li> |
73 output to trace mode</a>.</li> |
67 <li>Internal: This option will create a data file to the target |
74 <li><strong>Output to file system</strong>: This option will create a |
68 hardware. The data file name is the same as the project name. If |
75 data file to the target hardware. When using this option, you must |
69 you select the <b>Name from the user</b> option, you must define a |
76 define a location and name for the data file. For more information, |
70 name for the data file. For more information, see <a |
77 see <a href="../tasks/capture.htm#capture_s60_file">Capturing data |
71 href="../tasks/capture.htm#capture_s60_file">Capturing data in |
78 in output to file system mode</a> |
72 internal data gathering mode</a> |
|
73 <ul> |
79 <ul> |
74 <li>Name from the process: This option will a use data file name |
80 <li><strong>Log file path</strong>: Type here the location for |
75 which is the same as application target name.</li> |
81 the log file.</li> |
76 <li>Name from the user: This option will ask a data file name |
82 <li><strong>File name</strong>: Type here the name you want to |
77 every time a project is built with the <i>atool.exe</i>.</li> |
83 use for the log file</li> |
78 </ul> |
84 </ul> |
79 </li> |
85 </li> |
80 <li>Ask always: This option will ask before each build which data |
86 <li><strong>Ask always</strong>: When this option is selected, |
81 gathering mode to use, External or Internal</li> |
87 Analyse tool will display a dialog, asking which output mode you |
|
88 want to use, each time you build a project.</li> |
82 </ul> |
89 </ul> |
83 </td> |
90 </td> |
84 </tr> |
91 </tr> |
85 <tr> |
92 <tr> |
86 <td>Stored callstack size</td> |
93 <td>Stored callstack size</td> |
87 <td><ul> |
94 <td><ul> |
88 <li>No items. This option does not store any callstack items.</li> |
95 <li><strong>No callstack stored</strong>: This option does not store |
89 <li>40 items. This option stores forty callstack items.</li> |
96 any callstack items.</li> |
90 <li>100 items. This option stores hundred callstack items</li> |
97 <li><strong>40 items</strong>: This option stores forty callstack |
91 <li>Custom callstack size. This option provides possibility to define |
98 items.</li> |
92 custom size of callstack items. Custom size of callstack items is |
99 <li><strong>100 items</strong>: This option stores hundred callstack |
93 limited to 0-255</li> |
100 items. Note that storing this meni items </li> |
|
101 <li><strong>Custom size (0-255</strong>): This option provides |
|
102 possibility to define custom size of callstack items. Custom size |
|
103 of callstack items is limited to 0-255</li> |
94 </ul> |
104 </ul> |
95 <b>Note!</b> The callstack size affects the speed of hooked process, |
105 <b>Note!</b> The callstack size affects the speed of hooked process, |
96 lower callstack size is faster. </td> |
106 lower callstack size is faster. </td> |
97 </tr> |
107 </tr> |
98 <tr> |
108 <tr> |