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="../../book.css" rel="StyleSheet" type="text/css"> |
6 <link href="../../book.css" rel="StyleSheet" type="text/css"> |
7 <title>AnalyzeTool data file</title> |
7 <title>AnalyzeTool data file</title> |
8 </head> |
8 </head> |
|
9 |
9 <body> |
10 <body> |
|
11 <h2>AnalyzeTool files</h2> |
10 |
12 |
11 <h2>AnalyzeTool files</h2><p>AnalyzeTool uses files as follows:</p> |
13 <p>AnalyzeTool uses files as follows:</p> |
12 <ul> |
14 <ul> |
13 <li>Device data file. Data file saved to target device in <b>monitored internal</b> data gathering mode.</li> |
15 <li>Device data file. Data file saved to target device in <b>output to file |
14 <li>Raw data file. Analysis file saved after the trace is captured in <b>monitored external</b> or <b>external</b> data gathering mode.</li> |
16 system</b> mode.</li> |
15 <li>Memory leak results. Results file saved by user.</li> |
17 <li>Raw data file. Analysis file saved after the trace is captured in |
|
18 <b>output to trace</b> mode.</li> |
|
19 <li>Memory leak results. Results file saved by user.</li> |
16 </ul> |
20 </ul> |
17 <p>Any of these files can be opened by using the same button in <b>AnalyzeTool</b> view. AnalyzeTool automatically recognizes the file type, and performs the desired action.</p> |
21 |
|
22 <p>Any of these files can be opened by using the same button in |
|
23 <b>AnalyzeTool</b> view. AnalyzeTool automatically recognizes the file type, |
|
24 and performs the desired action.</p> |
18 |
25 |
19 <h4>Saving analysis data</h4> |
26 <h4>Saving analysis data</h4> |
20 <p>You can save the memory leak results or raw test run data. The difference between the file formats is that the raw test run data contains all available data collected during the test run, whereas the memory leak results file only contains the test results from the currently selected project. The memory leak results file can be opened and the results read without source codes, but the raw data always needs the source codes built with AnalyzeTool before it can be opened.</p> |
|
21 |
27 |
22 <div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. |
28 <p>You can save the memory leak results or raw test run data. The difference |
23 License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.</div> |
29 between the file formats is that the raw test run data contains all available |
|
30 data collected during the test run, whereas the memory leak results file only |
|
31 contains the test results from the currently selected project. The memory leak |
|
32 results file can be opened and the results read without source codes, but the |
|
33 raw data always needs the source codes built with AnalyzeTool before it can be |
|
34 opened.</p> |
|
35 |
|
36 <div id="footer"> |
|
37 Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights |
|
38 reserved. License: <a |
|
39 href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.</div> |
24 </body> |
40 </body> |
25 </html> |
41 </html> |