1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"> |
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 1.0 Transitional//EN"> |
2 <html> |
2 <html> |
3 <head> |
3 <head> |
4 <meta content="text/html; charset=us-ascii" http-equiv="content-type"> |
4 <meta content="text/html; charset=us-ascii" http-equiv="content-type"> |
5 <meta content="text/css" http-equiv="content-style-type"> |
5 <meta content="text/css" http-equiv="content-style-type"> |
6 <link href="../nokia.css" rel="StyleSheet" type="text/css"> |
6 <link href="../../book.css" rel="StyleSheet" type="text/css"> |
7 <title>Capturing data</title> |
7 <title>Capturing data</title> |
8 </head> |
8 </head> |
|
9 |
9 <body> |
10 <body> |
|
11 <h2>Capturing data</h2> |
10 |
12 |
11 <h2>Capturing data</h2> |
13 <p>There are two alternative ways to capture data, depending on the data |
12 <p>There are two alternative ways to capture data, depending on the data gathering mode.</p> |
14 gathering mode.</p> |
13 |
15 |
14 <h3 id="capture_external">Capturing data in monitored external or external data gathering mode</h3> |
16 <h3 id="capture_external">Capturing data in monitored external or external data |
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> |
17 gathering mode</h3> |
16 <p><b>Note!</b> This option requires that a tracing utility is available and a connection is established to the target hardware.</p> |
18 |
17 <p>USB tracing can not be run from the device bootup because it requires USB tracing activation from the device side.</p> |
19 <p><b>Note!</b> AnalyzeTool decides which connection method to use by checking |
|
20 the project active build configuration settings. If the active build |
|
21 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 |
|
23 <b>GCEE</b> build configurations AnalyzeTool captures data using the tracing |
|
24 utility connection.</p> |
|
25 |
|
26 <p><b>Note!</b> This option requires that a tracing utility is available and a |
|
27 connection is established to the target hardware.</p> |
|
28 |
|
29 <p>USB tracing can not be run from the device bootup because it requires USB |
|
30 tracing activation from the device side.</p> |
|
31 |
18 <p>To capture data:</p> |
32 <p>To capture data:</p> |
19 <ol> |
33 <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> |
34 <li>Open the <b>AnalyzeTool</b> view (if it is not already open) by selecting |
21 <li>Start capturing data by clicking <b>Start tracing</b> in the AnalyzeTool toolbar.</li> |
35 <b>Window > Show View > Other... > Carbide Extensions > |
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> |
36 AnalyzeTool.</b></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> |
37 <li>Start capturing data by clicking <b>Start tracing</b> in the AnalyzeTool |
|
38 toolbar. |
|
39 <p><strong>Note</strong> that at this point the system checks the version |
|
40 of the dbghelp.dll library provided by Windows. If the version is not at |
|
41 least 6.3.0.0, a confirmation dialog will appear with instructions on how |
|
42 to update a later version. </p> |
|
43 </li> |
|
44 <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 |
|
46 hardware.</li> |
|
47 <li>At the end of a test run, close the tested application (process). After |
|
48 you have closed the application, stop the test run by clicking <b>Stop |
|
49 tracing</b>. |
|
50 <p>Now AnalyzeTool has captured data, saved it into the project's |
|
51 <i>bld.inf\atool_temp</i> directory, and the memory analysis results are |
|
52 displayed in the <b>AnalyzeTool</b> view.</p> |
|
53 </li> |
24 </ol> |
54 </ol> |
25 <h3 id="capture_s60_file">Capturing data in monitored internal data gathering mode</h3> |
55 |
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> |
56 <h3 id="capture_s60_file">Capturing data in monitored internal data gathering |
|
57 mode</h3> |
|
58 |
|
59 <p>When you select the <b>monitored internal</b> data gathering mode in |
|
60 AnalyzeTool build, AnalyzeTool collects the test data into a file.</p> |
|
61 |
|
62 <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> |
|
64 |
27 <p>To capture data:</p> |
65 <p>To capture data:</p> |
28 <ol> |
66 <ol> |
29 <li>Install the AnalyzeTool software to the target hardware if not already installed.</li> |
67 <li>Install the AnalyzeTool software to the target hardware if not already |
30 <li>Install the test software built with AnalyzeTool to the target hardware.</li> |
68 installed.</li> |
31 <li>Start the application built with AnalyzeTool in the target hardware, and run the desired test cases.</li> |
69 <li>Install the test software built with AnalyzeTool to the target |
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>. |
70 hardware.</li> |
33 <p><b>Note!</b> The data file name was specified before the build.</p></li> |
71 <li>Start the application built with AnalyzeTool in the target hardware, and |
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> |
72 run the desired test cases.</li> |
|
73 <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 |
|
75 saved in <i>e:\analyzetool\</i> or <i>c:\data\analyzetool\</i> depending if |
|
76 the memory card is used or not. In the emulator environment the file is |
|
77 saved in <i>\epoc32\winscw\c\logs\analyzetool\</i>. |
|
78 <p><b>Note!</b> The data file name was specified before the build.</p> |
|
79 </li> |
|
80 <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 |
|
82 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> |
35 </ol> |
84 </ol> |
36 |
85 |
37 <div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. |
86 <div id="footer"> |
38 License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.</div> |
87 Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights |
|
88 reserved. License: <a |
|
89 href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.</div> |
39 </body> |
90 </body> |
40 </html> |
91 </html> |