|
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> |
|
2 <html> |
|
3 <head> |
|
4 <meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> |
|
5 <title>TraceAnalyser basic walk-through</title> |
|
6 <link href="../../book.css" type="text/css" rel="stylesheet"></head> |
|
7 <body><h2>TraceAnalyser basic walk-through</h2> <h5>Before you start</h5><p> |
|
8 Setting up TraceAnalyser requires the following tracing tools: </p><ul> |
|
9 <li><b>In Carbide.c++:</b> TraceBuilder and TraceViewer tools, accessible |
|
10 from the <b>Carbide</b> menu. </li> |
|
11 <li><b>In the device:</b> (Optional) The TraceSwitch tool that listens to |
|
12 the incoming traces. For more information on how to obtain it, see the <a |
|
13 href="../release_notes.htm#requirements">Release Note</a><?Pub Caret1>. </li> |
|
14 </ul><p>The following steps are needed for using this tool: </p><ol> |
|
15 <li>Open or create a project in Carbide.c++. </li> |
|
16 <li>To add OST traces to the source code, start the TraceBuilder tool from <b> |
|
17 Carbide > TraceBuilder</b>. <p> For more instructions, see the topic <i>Adding |
|
18 traces to the source code</i> in TraceBuilder Help. </p></li> |
|
19 <li>Set your project's include paths and compile the application. For instructions, |
|
20 see <i>Setting project include paths and compiling</i> in TraceBuilder Help. <p><b> |
|
21 Note:</b> Compilation uses TraceCompiler that generates the needed headers. |
|
22 After compilation, you should have two files: </p><ul> |
|
23 <li>a SIS file of your tool that you can now install into the device. </li> |
|
24 <li>an XML format dictionary file that is needed for activating and decoding |
|
25 traces in TraceViewer. It is generated into the following directory: <i>[SDK |
|
26 root]\epoc32\include\internal\symbiantraces\dictionary</i>. </li> |
|
27 </ul></li> |
|
28 <li>In TraceViewer, also define the settings for connecting your PC to the |
|
29 device. The options are USB or eXtended Trace Interface (XTI). <p>See <i> |
|
30 Setting TraceViewer preferences</i> in TraceViewer Help. </p><p><b>Tip:</b> If |
|
31 you have TraceSwitch enabled in the device, the USB connection is supported |
|
32 by default and you only need to plug in the device to start receiving traces. |
|
33 </p></li> |
|
34 <li>To activate and decode traces, start the TraceViewer tool from <b>Carbide |
|
35 > TraceViewer</b>, and activate the dictionary file there. <p>For instructions, |
|
36 see <i>Trace activation </i> in TraceViewer Help. </p></li> |
|
37 <li>In TraceAnalyser, create the rules for issues you want to monitor: timings |
|
38 or parameters. <p>See example scenarios in <i>TraceAnalyser overview</i> and |
|
39 step-by-step instructions in <a href="../tasks/creating_rules.htm">Creating |
|
40 tracing rules</a>. </p></li> |
|
41 <li>Transfer your application's SIS file to the device and run it. <p>If some |
|
42 tracing rules fail during execution, they are listed on the TraceAnalyser's <b> |
|
43 Fail Log</b> tab.</p></li> |
|
44 <li>To analyse the failed rule in more detail, double-click it to view it |
|
45 in the TraceViewer application. TraceViewer will show the codeline that caused |
|
46 the failure.</li> |
|
47 </ol><div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. |
|
48 License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.</div> </body></html> |