8 </head> |
8 </head> |
9 |
9 |
10 <body> |
10 <body> |
11 <h2>Capturing data</h2> |
11 <h2>Capturing data</h2> |
12 |
12 |
13 <p>There are two alternative ways to capture data, depending on the data |
13 <p>There are two alternative ways to capture data, depending on the output |
14 gathering mode.</p> |
14 mode.</p> |
15 |
15 |
16 <h3 id="capture_external">Capturing data in monitored external or external data |
16 <h3 id="capture_external">Capturing data in output to trace mode</h3> |
17 gathering mode</h3> |
|
18 |
17 |
19 <p><b>Note!</b> AnalyzeTool decides which connection method to use by checking |
18 <p><b>Note!</b> AnalyzeTool decides which connection method to use by checking |
20 the project active build configuration settings. If the active build |
19 the project active build configuration settings. If the active build |
21 configuration is set to <b>WINSCW</b>, AnalyzeTool captures data from the |
20 configuration is set to <b>WINSCW</b>, AnalyzeTool captures data from the |
22 emulator output file <i>(%tmp%\epocwind.out)</i>; in <b>ARMV5</b> and |
21 emulator output file <i>(%tmp%\epocwind.out)</i>; in <b>ARMV5</b> and |
34 <li>Open the <b>AnalyzeTool</b> view (if it is not already open) by selecting |
33 <li>Open the <b>AnalyzeTool</b> view (if it is not already open) by selecting |
35 <b>Window > Show View > Other... > Carbide Extensions > |
34 <b>Window > Show View > Other... > Carbide Extensions > |
36 AnalyzeTool.</b></li> |
35 AnalyzeTool.</b></li> |
37 <li>Start capturing data by clicking <b>Start tracing</b> in the AnalyzeTool |
36 <li>Start capturing data by clicking <b>Start tracing</b> in the AnalyzeTool |
38 toolbar. |
37 toolbar. |
39 <p><strong>Note</strong> that at this point the system checks the version |
38 <p class="note">NOTE that at this point the system checks the version of |
40 of the dbghelp.dll library provided by Windows. If the version is not at |
39 the dbghelp.dll library provided by Windows. If the version is not at least |
41 least 6.3.0.0, a confirmation dialog will appear with instructions on how |
40 6.3.0.0, a confirmation dialog will appear with instructions on how to |
42 to update a later version. </p> |
41 update a later version. </p> |
43 </li> |
42 </li> |
44 <li>Start the application built with AnalyzeTool, and run the desired test |
43 <li>Start the application built with AnalyzeTool, and run the desired test |
45 cases. Note that Carbide.c++ needs to be connected to the target |
44 cases. Note that Carbide.c++ needs to be connected to the target |
46 hardware.</li> |
45 hardware.</li> |
47 <li>At the end of a test run, close the tested application (process). After |
46 <li>At the end of a test run, close the tested application (process). After |
51 <i>bld.inf\atool_temp</i> directory, and the memory analysis results are |
50 <i>bld.inf\atool_temp</i> directory, and the memory analysis results are |
52 displayed in the <b>AnalyzeTool</b> view.</p> |
51 displayed in the <b>AnalyzeTool</b> view.</p> |
53 </li> |
52 </li> |
54 </ol> |
53 </ol> |
55 |
54 |
56 <h3 id="capture_s60_file">Capturing data in monitored internal data gathering |
55 <h3 id="capture_s60_file">Capturing data in output to file system mode</h3> |
57 mode</h3> |
|
58 |
56 |
59 <p>When you select the <b>monitored internal</b> data gathering mode in |
57 <p>When you select the <b>output to file system</b> mode in AnalyzeTool build, |
60 AnalyzeTool build, AnalyzeTool collects the test data into a file.</p> |
58 AnalyzeTool collects the test data into a file.</p> |
61 |
59 |
62 <p><b>Note!</b> If you are analyzing an application in the target hardware, the |
60 <p><b>Note!</b> If you are analyzing an application in the target hardware, the |
63 file must be transferred to a PC after the test run is completed.</p> |
61 file must be transferred to a PC after the test run is completed.</p> |
64 |
62 |
65 <p>To capture data:</p> |
63 <p>To capture data:</p> |
69 <li>Install the test software built with AnalyzeTool to the target |
67 <li>Install the test software built with AnalyzeTool to the target |
70 hardware.</li> |
68 hardware.</li> |
71 <li>Start the application built with AnalyzeTool in the target hardware, and |
69 <li>Start the application built with AnalyzeTool in the target hardware, and |
72 run the desired test cases.</li> |
70 run the desired test cases.</li> |
73 <li>At the end of a test run, close the tested application (process). This |
71 <li>At the end of a test run, close the tested application (process). This |
74 will write the test data to a file. In the target hardware the file is |
72 will write the test data to a file. |
75 saved in <i>e:\analyzetool\</i> or <i>c:\data\analyzetool\</i> depending if |
73 <p class="note">NOTE The name of the file and the location where the file |
76 the memory card is used or not. In the emulator environment the file is |
74 is saved in the target hardware are defined in the AnalyzeTool |
77 saved in <i>\epoc32\winscw\c\logs\analyzetool\</i>. |
75 preferences.</p> |
78 <p><b>Note!</b> The data file name was specified before the build.</p> |
76 <p>In the emulator environment the file is saved in |
|
77 <i>\epoc32\winscw\c\logs\analyzetool\</i>. </p> |
79 </li> |
78 </li> |
80 <li>While the tested software project is active in the <b>Project |
79 <li>While the tested software project is active in the <b>Project |
81 Explorer</b>, open the data file by clicking <b>Open and analyze data |
80 Explorer</b>, open the data file by clicking <b>Open and analyze data |
82 file</b> in the <b>AnalyzeTool</b> toolbar. This will run the analysis and |
81 file</b> in the <b>AnalyzeTool</b> toolbar. This will run the analysis and |
83 display the results in the <b>AnalyzeTool</b> view.</li> |
82 display the results in the <b>AnalyzeTool</b> view.</li> |