|
1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"> |
|
2 <html> |
|
3 <head> |
|
4 <meta content="text/html; charset=us-ascii" http-equiv="content-type"> |
|
5 <meta content="text/css" http-equiv="content-style-type"> |
|
6 <link href="../nokia.css" rel="StyleSheet" type="text/css"> |
|
7 <title>Capturing data</title> |
|
8 </head> |
|
9 <body> |
|
10 |
|
11 <h2>Capturing data</h2> |
|
12 <p>There are two alternative ways to capture data, depending on the data gathering mode.</p> |
|
13 |
|
14 <h3 id="capture_external">Capturing data in monitored external or external data gathering mode</h3> |
|
15 <p><b>Note!</b> AnalyzeTool decides which connection method to use by checking the project active build configuration settings. If the active build configuration is set to <b>WINSCW</b>, AnalyzeTool captures data from the emulator output file <i>(%tmp%\epocwind.out)</i>; in <b>ARMV5</b> and <b>GCEE</b> build configurations AnalyzeTool captures data using the tracing utility connection.</p> |
|
16 <p><b>Note!</b> This option requires that a tracing utility is available and a connection is established to the target hardware.</p> |
|
17 <p>USB tracing can not be run from the device bootup because it requires USB tracing activation from the device side.</p> |
|
18 <p>To capture data:</p> |
|
19 <ol> |
|
20 <li>Open the <b>AnalyzeTool</b> view (if it is not already open) by selecting <b>Window > Show View > Other... > Carbide Extensions > AnalyzeTool.</b></li> |
|
21 <li>Start capturing data by clicking <b>Start tracing</b> in the AnalyzeTool toolbar.</li> |
|
22 <li>Start the application built with AnalyzeTool, and run the desired test cases. Note that Carbide.c++ needs to be connected to the target hardware.</li> |
|
23 <li>At the end of a test run, close the tested application (process). After you have closed the application, stop the test run by clicking <b>Stop tracing</b>. <p>Now AnalyzeTool has captured data, saved it into the project's <i>bld.inf\atool_temp</i> directory, and the memory analysis results are displayed in the <b>AnalyzeTool</b> view.</p></li> |
|
24 </ol> |
|
25 <h3 id="capture_s60_file">Capturing data in monitored internal data gathering mode</h3> |
|
26 <p>When you select the <b>monitored internal</b> data gathering mode in AnalyzeTool build, AnalyzeTool collects the test data into a file.</p><p><b>Note!</b> If you are analyzing an application in the target hardware, the file must be transferred to a PC after the test run is completed.</p> |
|
27 <p>To capture data:</p> |
|
28 <ol> |
|
29 <li>Install the AnalyzeTool software to the target hardware if not already installed.</li> |
|
30 <li>Install the test software built with AnalyzeTool to the target hardware.</li> |
|
31 <li>Start the application built with AnalyzeTool in the target hardware, and run the desired test cases.</li> |
|
32 <li>At the end of a test run, close the tested application (process). This will write the test data to a file. In the target hardware the file is saved in <i>e:\analyzetool\</i> or <i>c:\data\analyzetool\</i> depending if the memory card is used or not. In the emulator environment the file is saved in <i>\epoc32\winscw\c\logs\analyzetool\</i>. |
|
33 <p><b>Note!</b> The data file name was specified before the build.</p></li> |
|
34 <li>While the tested software project is active in the <b>Project Explorer</b>, open the data file by clicking <b>Open and analyze data file</b> in the <b>AnalyzeTool</b> toolbar. This will run the analysis and display the results in the <b>AnalyzeTool</b> view.</li> |
|
35 </ol> |
|
36 |
|
37 <div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. |
|
38 License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.</div> |
|
39 </body> |
|
40 </html> |