# HG changeset patch # User Matti Laitinen # Date 1277290676 -10800 # Node ID 14dc2103a631ebb0330329683d60f69ceded0254 # Parent 15296fd0af4a3eb2da4158514071e584d281231e TraceAnalyser 1.0.5 diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.carbide.extensions.traceanalyser/build.properties --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.carbide.extensions.traceanalyser/build.properties Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,3 @@ +bin.includes = feature.xml,\ + license.txt,\ + license.htm diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.carbide.extensions.traceanalyser/feature.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.carbide.extensions.traceanalyser/feature.xml Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,62 @@ + + + + + Trace Analyser tool is used for analysing OST trace data that is received from a device. + + + + Nokia Corporation and/or its subsidiary(-ies). All rights reserved. License: http://www.eclipse.org/legal/epl-v10.html. + + + + Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies).All rights reserved. + This component and the accompanying materials are made available under the + terms of "Eclipse Public License v1.0" which accompanies this + distribution, and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". + + Part of the graphics of the program are from Eclipse 3.1 platform + and CDT project in Eclipse community, which are made available under + the terms of the Eclipse Public License v1.0. + A copy of the EPL is provided at + http://www.eclipse.org/legal/epl-v10.html + + + + + + + + + + + + + + + diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.carbide.extensions.traceanalyser/license.htm --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.carbide.extensions.traceanalyser/license.htm Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,14 @@ +

Carbide.c++ Extensions - TraceViewer plug-in

+ +

License Information

+COPYRIGHTS
+Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies).All rights reserved.
+This component and the accompanying materials are made available under the
+terms of "Eclipse Public License v1.0" which accompanies this
+distribution, and is available at the URL "http://www.eclipse.org/legal/epl-v10.html".
+ +Part of the graphics of the program are from Eclipse 3.1 platform +and CDT project in Eclipse community, which are made available under +the terms of the Eclipse Public License v1.0. +A copy of the EPL is provided at +http://www.eclipse.org/legal/epl-v10.html \ No newline at end of file diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/META-INF/MANIFEST.MF --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/META-INF/MANIFEST.MF Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,6 @@ +Manifest-Version: 1.0 +Bundle-ManifestVersion: 1 +Bundle-Name: External Tool Help Template Plug-in +Bundle-SymbolicName: com.nokia.s60tools.traceanalyser.help;singleton=true +Bundle-Version: 1.0.3 +Bundle-Vendor: Nokia diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/about.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/about.html Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,25 @@ + + + + About + + + + +

About This Content

+ +

June, 2010

+ +

Copyright

+ +

Copyright � 2010 Nokia Corporation and/or its subsidiary(-ies). All rights +reserved.
+License: http://www.eclipse.org/legal/epl-v10.html.

+ +

+ + diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/book.css --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/book.css Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,183 @@ +/* + Copyright (c) 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. + License: http://www.eclipse.org/legal/epl-v10.html +*/ + +/* Add whitespace around entire display to avoid crowding edges of view */ +/* 20070523-Removed top margin size to close gap between location breadcrumbs and page title */ +html { + margin: 2px 10px 10px 10px; + } + +/* Set default font to serif style, 12-pt and plain */ +body, p, table { + font-family: Verdana, Helvetica, Arial, sans-serif; + font-size: 13px; + font-weight: normal; +} + +/* Use sans-serif fonts for all title styles */ +h1, h2, h3, h4, h5, h6, strong, em { + font-family: Verdana, Helvetica, Arial, sans-serif; + color: #000000; + } + +h1 { font-size:20px } +h2 { font-size:18px } +h3 { font-size:16px } +h4 { font-size:14px } +h5 { font-size:13px } +h6 { font-size:12px } + +/* For headlines at the top of a view, add space */ +/* 20090224-changed green fade to gold header image */ +h1, h2, h3 { + background-image: url(html/images/gold_header.png); + background-repeat: no-repeat; + padding:10px 0px 10px 12px; + } + +li { + margin-bottom:8px; + margin-top:8px; + } + +/* Footer includes space and a gray line above the company logo */ +#footer { + padding-top:10px; + margin-top:20px; + border-top:1px solid #999; + font-family: Helvetica, sans-serif; + font-size: 11px; + color:#333; + } + +.listing { + font-family: "Courier New", Courier, mono; + color: #000000; + background-color: #FFFFCC; + margin: 5px 0px; + } + +.code, pre { + font-family: "Courier New", Courier, mono; + font-size: 13px; + color: #000000; + } + +.step { + /* background-color: #EEE; */ + /* margin: 10px 0px; */ + /* color: #111; */ + /* border-bottom:2px solid #EEE; */ + } + +.substep { + background-color: #EEE; + } + + +/* Figure/Listing/Table titles are centered and gray */ +p.table { + color: #999; + font-weight: bold; + padding-top: 5px; + } + +table { + border: solid #999 1px; + table-layout: auto; + font-size: 13px; + } + +td, th { + border: solid #999 1px; + padding: 5px; + vertical-align:top; + } + +/* 20070522-replaced gray with green background to match gradiant color for title */ +th { + background-color:#FFC550; /* background-color:#acd79b; + background-color:#999; + color:#FFF; */ + } + +div.ol.p { + margin-left: 3em; + } + +/* Make all ordered/unordered list items appear in bold gray */ +div ol > li, div ul > li { + font-weight:bold; + color: #333; + } + +div ol > p, div ul > p, div li > p { + font-weight:normal; + } + +/* Make all H4 and H5 items appear in bold gray against a light green background */ +div h5, div h4 { + padding:5px 0px 5px 12px; + background-color:#FDCB2F; + /* background-color: #EEE; */ + font-weight:bold; + color: #000000; + } + + +/* Notes stand out using a light top & bottom borders with dark gray text */ +p.note { + /* color: #03C; */ + /* background-color: #FFFF99; */ + color: #333; + padding: 5px; + margin-left: 1em; + margin-right: 1em; + border-top: solid #BBB thin; + border-bottom: solid #BBB thin; + } + + +/* Figure/Listing/Table titles are centered and gray */ +p.figure { + color: #333; + text-align: center; + font-weight: bold; + } + +/* highly visible red background and white text for things that need fixing before release */ +/* SHOULD NOT BE PRESENT IN RELEASED PRODUCTS */ +.fix { + background-color: red; + font-weight: bold; + color: white; + } + +.question { + font-style:italic; + font-weight:bold; + color: #555; + } + +.titleSmall { + font-family: Helvetica, sans-serif; + font-size: 11px; + } + + +.plain { + font-family: Helvetica, sans-serif; + font-size: 12px; + font-style: normal; + line-height: normal; + font-weight: normal; + font-variant: normal; + color: #000000; + text-decoration: none; + } + +a:link { color: #0033CC } +a:visited { color: #555555 } +a:hover { color: #0033CC } diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/build.properties --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/build.properties Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,8 @@ +bin.includes = META-INF/,\ + html/,\ + plugin.xml,\ + book.css +src.includes = html/,\ + META-INF/,\ + plugin.xml,\ + book.css diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/cheatsheet/getStarted_ta_cs.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/cheatsheet/getStarted_ta_cs.xml Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,140 @@ + + + + + + + + +This tutorial shows you the steps for creating tracing rules in the TraceAnalyser tool. +

+Prerequisites +

+* TraceViewer and TraceBuilder applications are present in your Carbide.c++ environment. +

+* (Optional) TraceSwitch SIS is installed on your device. +

+You can obtain TraceSwitch from the S60 RnD SDK, under the RnD Tools folder. TraceSwitch, together with the ToolsStarter SIS, support the USB connection method by default. You only need to plug in the device to start receiving traces. + + + + +Open or create a new project in Carbide.c++. + + + + +Adding Open System Traces (OST) means adding "tags" to your application's source code, to those places that you want to monitor. +
+
+The easiest way to do this is by using the TraceBuilder application: Carbide > TraceBuilder. +
+
+For example, to monitor timings in a camera application, you could add the first trace to capture the key press for taking a picture, and another where the taken picture is shown to the user. +
+
+The corresponding rule to be created in TraceAnalyser might then state that these actions must occur within 5 seconds. + + + + + To use Open System Trace (OST) traces, you must include the "OpenSystemTrace.h" header file from the development environment. +

+ + + + + After compiling your project, you should have two files: +

+1: A SIS file of your application that you can install into the device by using USB. +

+2: An XML format dictionary file that is needed for activating and decoding traces in TraceViewer. +

+The file is generated into the following directory: +

+[SDK root]\epoc32\include\internal\symbiantraces\dictionary. + + + + + + To start receiving traces on the TraceViewer application, define connection settings between the device and your PC. +

+Start the TraceViewer tool from Carbide > TraceViewer. +

+On the toolbar, click the small arrow and from the drop-down list, select Connection Settings. +

+ + + + + Trace activation is a way of generating specific trace data that is relevant for your components. This reduces the amount of traces listed on the TraceViewer user interface. +

+Start the TraceViewer tool from Carbide > TraceViewer. +

+Load the dictionary file (.xml) that contains the necessary component and group information. +

+Activate the components and groups you want to use. +

+For more information, see TraceViewer Help. + + + + + Start TraceAnalyser from Carbide > TraceAnalyser. +

+Create either Timing or Parameter rule type for the events you want to monitor. +

+An example of the rule could be a statement like this: "Taking a picture should not take longer than 5 seconds." + + + + + In TraceViewer, start receiving traces. +

+Run the SIS file of your application on the device. + + + + + All executed trace rules (both passed and failed ones) are listed on the TraceAnalyser main view. +

+If some of them fail during execution (for example, an operation execution takes longer than defined in the rule), the TraceAnalyser icon will quickly flash to indicate that a rule violation has occurred. +

+To view the failed cases, select the Fail Log tab. +

+To view the traces that caused the failure, double-click a rule on the view. TraceViewer opens and scrolls to the traces. +

+Double-click the trace to jump to the codeline that caused the failure. + + + + + + To view the traces that caused the failure, double-click a rule on the TraceAnalyser Fail Log. +

+TraceViewer opens and scrolls to the trace. +

+In TraceViewer, double-click the trace to jump to the codeline that caused the failure. +

+Once you have identified the problem in the source code, try to fix it and run the rule again. + + + + diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/contexts.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/contexts.xml Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,71 @@ + + + + + + + + + + + + + + In TraceAnalyser, you can create rules to supervise the time consumption of an application and detect timing violations. The main view shows both passed and failed rules. + + + + + + If a tracing rule fails (for example, the interval between operations is longer than defined), you can view more information about the violation on the Fail Log tab. + + + + + TraceAnalyser's Rule Editor dialog contains general fields for all rule types, and some specific fields for timing and parameter rules separately. + + + + + + In the Trace Selection dialog, you can view the trace dictionaries that are loaded in TraceViewer application, and select the traces you want to use. + + + + + TraceAnalyser history view shows you information on the rule's performance over time. + + + + diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/gettingstarted/gs_index.htm --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/gettingstarted/gs_index.htm Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,19 @@ + + + + + +Getting started + + + +

Getting started

The following topics give you information on how to get started with this tool:

+ + + diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/gettingstarted/images/dg_mainview.png Binary file trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/gettingstarted/images/dg_mainview.png has changed diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/gettingstarted/traceanalyser_basic_walkthrough.htm --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/gettingstarted/traceanalyser_basic_walkthrough.htm Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,48 @@ + + + + +TraceAnalyser basic walk-through + +

TraceAnalyser basic walk-through

Before you start

+Setting up TraceAnalyser requires the following tracing tools:

In Carbide.c++: TraceBuilder and TraceViewer tools, accessible +from the Carbide menu.
In the device: (Optional) The TraceSwitch tool that listens to +the incoming traces. For more information on how to obtain it, see the Release Note.

The following steps are needed for using this tool:

Open or create a project in Carbide.c++.
To add OST traces to the source code, start the TraceBuilder tool from +Carbide > TraceBuilder.
For more instructions, see the topic Adding +traces to the source code in TraceBuilder Help.
Set your project's include paths and compile the application. For instructions, +see Setting project include paths and compiling in TraceBuilder Help.
+Note: Compilation uses TraceCompiler that generates the needed headers. +After compilation, you should have two files:
- a SIS file of your tool that you can now install into the device.
- an XML format dictionary file that is needed for activating and decoding +traces in TraceViewer. It is generated into the following directory: [SDK +root]\epoc32\include\internal\symbiantraces\dictionary.
In TraceViewer, also define the settings for connecting your PC to the +device. The options are USB or eXtended Trace Interface (XTI).
See +Setting TraceViewer preferences in TraceViewer Help.
Tip: If +you have TraceSwitch enabled in the device, the USB connection is supported +by default and you only need to plug in the device to start receiving traces. +
To activate and decode traces, start the TraceViewer tool from Carbide +> TraceViewer, and activate the dictionary file there.
For instructions, +see Trace activation in TraceViewer Help.
In TraceAnalyser, create the rules for issues you want to monitor: timings +or parameters.
See example scenarios in TraceAnalyser overview and +step-by-step instructions in Creating +tracing rules.
Transfer your application's SIS file to the device and run it.
If some +tracing rules fail during execution, they are listed on the TraceAnalyser's +Fail Log tab.
To analyse the failed rule in more detail, double-click it to view it +in the TraceViewer application. TraceViewer will show the codeline that caused +the failure.

diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/gettingstarted/traceanalyser_overview.htm --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/gettingstarted/traceanalyser_overview.htm Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,36 @@ + + + + +TraceAnalyser overview + +

TraceAnalyser overview

TraceAnalyser is a tool that enables +you to supervise the target application's time consumption during an operation, +or supervise parameters in Open System Trace (OST) traces.

With this +tool, you can create a set of rules that define:

the order and maximum delay between two operations that are traced (see +example scenario below).
a desired range for parameter values (for example, "The first parameter +of Trace A should be at least 150").

TraceAnalyser lists both passed and failed events to the main view, +along with other information such as the pass rate. See the following example: +

Sample view of data filled in on the tabbed view.

+If a rule fails (for example, the interval between operations is longer than +defined), you can view more information about the violation on the Fail +Log tab.

You can also view history graphs of the defined rules, +to see how the performance of your application has changed over time.

Example: Analysing timings in a camera application

+When developing a camera application, you might want to define the following +kind of rule:

“Taking a picture should not take longer than +5 seconds.”

To monitor this programmatically, you can instrument +your code so that OST trace is placed to capture the key press for taking +a picture, and another where the taken picture is shown to the user. The corresponding +rule would then state that these actions must occur within 5 seconds.

+Related Tasks

diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/images/about_cpp.png Binary file trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/images/about_cpp.png has changed diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/images/background_carbide.jpg Binary file trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/images/background_carbide.jpg has changed diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/images/brandmark_cpp.gif Binary file trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/images/brandmark_cpp.gif has changed diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/images/gold_header.png Binary file trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/images/gold_header.png has changed diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/images/green_fade_left_68_165_28.png Binary file trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/images/green_fade_left_68_165_28.png has changed diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/index.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/index.xml Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,95 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/intro/overviewTraceAnalyserExtContent.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/intro/overviewTraceAnalyserExtContent.xml Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,28 @@ + + + + + + + + + + + Learn about Trace Analyser and what it can do to improve your development efforts. + + + + + + + diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/intro/traceanalyser.css --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/intro/traceanalyser.css Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,2 @@ +a#traceanalyser img { background-image : url(traceanalyser.gif); } +a#traceanalyser:hover img { background-image : url(traceanalyser_hov.gif); } diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/intro/traceanalyser.gif Binary file trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/intro/traceanalyser.gif has changed diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/intro/traceanalyser.properties --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/intro/traceanalyser.properties Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,9 @@ + +overview.traceanalyser = html/intro/traceanalyser.gif +overview.traceanalyser:hover = html/intro/traceanalyser_hov.gif + +whatsnew.traceanalyser = html/intro/traceanalyser.gif +whatsnew.traceanalyser:hover = html/intro/traceanalyser_hov.gif + +tutorials.traceanalyser = html/intro/traceanalyser.gif +tutorials.traceanalyser:hover = html/intro/traceanalyser_hov.gif diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/intro/traceanalyser_hov.gif Binary file trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/intro/traceanalyser_hov.gif has changed diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/intro/tutorialsTraceAnalyserExtContent.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/intro/tutorialsTraceAnalyserExtContent.xml Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,27 @@ + + + + + + + + + + + Start analysing traces by following step-by-step instructions. + + + + + + diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/intro/whatsnewTraceAnalyserExtContent.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/intro/whatsnewTraceAnalyserExtContent.xml Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,28 @@ + + + + + + + + + + + Learn about what's new in Trace Analyser for this release. + + + + + + + diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/legal.htm --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/legal.htm Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,38 @@ + + + + + License Information + + + + +

License Information

+ +

COPYRIGHTS

+ +

Copyright � 2010 Nokia Corporation and/or its subsidiary(-ies). All rights +reserved. This component and the accompanying materials are made available +under the terms of "Eclipse Public License v1.0" which accompanies this +distribution and is available at the URL http://www.eclipse.org/legal/epl-v10.html.

+ +

Initial Contributors:
+Nokia Corporation - initial contribution

+ +

NOTICES

+ +

Part of the graphics of the program are from Eclipse 3.1 platform and CDT +project in Eclipse community, which are made available under the terms of the +Eclipse Public License v1.0.

+ +

A copy of the EPL is provided at http://www.eclipse.org/legal/epl-v10.html +

+ + + + diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/release_notes.htm --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/release_notes.htm Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,134 @@ + + + + + Release Notes + + + + +

Release Notes

+ +

TraceAnalyser – Version 1.0.5

+ +

Released June 20, 2010

Product description
Main features
What's new
Installation notes
System requirements
Compatibility issues
Known issues

+ +

Product description

+ +

TraceAnalyser is a tool that enables you to supervise the target +application's time consumption during an operation, or supervise parameters in +Open System Trace (OST) traces.

+ +

The tool can be started by selecting the Carbide > TraceAnalyser +menu item.

+ +

Main features

+ +

With this tool, you can create a set of rules that define:

the order and maximum delay between two operations that are traced,
the desired range for parameter values.

+ +

TraceAnalyser lists both passed and failed events to the main view, along +with other information such as the pass rate.

+ +

What's new

TraceAnalyser is now released under EPL license.

+ +

Installation notes

+ +

System requirements

+ +

Basic requirements:

Windows 2000, Windows XP
Minimum SDK build PC.
Normal SDK build PC.

+ +

Additional requirements:

USB connection for connecting your PC to the device.
Nokia PC Suite for transferring files from your PC to the device.
TraceViewer for activating and viewing the received traces. Available in + the Carbide.c++ IDE.
(Optional) TraceBuilder for adding OST traces to your application code. + Available in the Carbide.c++ IDE.
(Optional) TraceSwitch SIS file installed on the device. Available in S60 + RnD platform releases, under the RnD Tools folder (source directory: + \ppd_sw\rd_sw\traceswitch). +
Together with the ToolsStarter SIS file, TraceSwitch enables an easy + plug-and-play tracing solution. For more information, see the + TraceSwitch User's Guide, available in the source directory.
+

+ +

Compatibility issues

+ +

Known issues

+ +

Version history

+ +

Version 1.0.4 – 8th December 2009

+ +

Bug fixes related to Help

+ +

Version 1.0.3 – 8th December 2009

+ +

Bug fixes related to usage of TraceViewer API. Scrolled traces are now +filtered out from analysed traces.

+ +

Version 1.0.2 – 6th October 2009

+ +

Bug fixes related tousage of TraceViewer API. Traces received from +TraceViewer are not anymore cloned.

+ +

Version 1.0.1 – 19th August 2009

+ +

Bug fixes in help links.

+ +

Version 1.0.0 – 25th June 2009

+ +

The first version.

+ + + + diff -r 15296fd0af4a -r 14dc2103a631 trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/tasks/creating_rules.htm --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/trace/traceanalyser/com.nokia.s60tools.traceanalyser.help/html/tasks/creating_rules.htm Wed Jun 23 13:57:56 2010 +0300 @@ -0,0 +1,85 @@ + + + + + +Creating tracing rules + +

Creating tracing rules

Before you start

Before you +can create tracing rules, check that you have:

compiled your code,
and loaded the generated dictionary file to TraceViewer.

See +TraceAnalyser basic walk-through for the complete steps.

To create +tracing rules, do the following:

Start TraceAnalyser from the Carbide > TraceAnalyser menu item. +
Click Create new rule.
The Edit Rule dialog is displayed. +
From the Rule Type list box, select which kind of rule you are +creating:
- Timing rule for detecting if an operation can be executed within +a specified time limit.
- Trace parameter rule for detecting if parameters are beyond a desireable +value range.
In the Rule Name field, type in a name for the rule.
For example: +Camera Test.
(Optional) In the Description field, type in a free-form description +of what the rule is about.
For example, for a timing rule: Test that +the Camera application is able to capture a picture within 1000ms time limit. +
Configure the rule-specific settings.
For instructions, see either To define timing rules or To define +parameter rules below.
Connect your PC to the device by using the connection settings defined +in TraceViewer (USB or XTI).
In TraceViewer, activate the traces you want to receive.
Run your application on the device.
During execution, TraceAnalyser +lists both passed and failed events to the main view, along with other information +such as the pass rate. See the following example:

After the rules have been executed, you can do either of the following: +

View the log of failed rules, and +together with TraceViewer determine which codeline caused the rule violation. +
View the rule history graph to see +how the performance of the application has changed over time.

To define timing rules:

To select which trace should be monitored as the first part of this rule +(Trace A), click Select Trace.
The Select Trace for Rule dialog +is opened, showing the trace dictionaries that you loaded in TraceViewer earlier. +
Select the traces you want to use and click OK.
Repeat the above steps for Trace B.
In the Time Limit fields, enter the range the values in milliseconds +for Trace A and Trace B.
- For Time Limit A, the value means that Trace B must arrive after +this.
- For Time Limit B, the value means that Trace B must arrive before +this.
The following figure shows an example of how a tracing rule could +look like:
To finish, click OK.