sysperfana/analyzetoolext/com.nokia.s60tools.analyzetool.help/html/release_notes.htm
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
<title>Release Notes</title>
<link href="../book.css" type="text/css" rel="stylesheet">
</head>
<body>
<h2>Release note</h2>
<h4>AnalyzeTool Carbide.c++ Extension – Version 1.10.0</h4>
<p>Released 30th June 2010</p>
<ul>
<li><a href="#description">Product description</a></li>
<li><a href="#features">Main features</a></li>
<li><a href="#newfeatures">What's new</a></li>
<li><a href="#installation">Installation notes</a></li>
<li><a href="#requirements">System requirements</a></li>
<li><a href="#compissues">Compatibility issues</a></li>
<li><a href="#issues">Known issues</a></li>
</ul>
<h3><a name="description"></a>Product description</h3>
<p>AnalyzeTool is a dynamic test tool that is used for testing Symbian software
for memory and resource leaks and pinpointing the leaks from the source
code.</p>
<p>For a general questions about the tool <a
href="https://s60wiki.nokia.com/S60Forum/forumdisplay.php?f=183">Dynamic
Analysis Tools discussion forum</a> can be used.</p>
<p>For more specific questions AnalyzeTool has e-mail list <a
href="mailto:AnalyzeTool_Support@lists.research.nokia.com">AnalyzeTool_Support@lists.research.nokia.com</a>
to contact project team and other users directly.</p>
<h3><a name="features"></a>Main features</h3>
<ul>
<li>UI for activating a memory leak analysis. </li>
<li>UI for seeing results of a memory leak analysis.</li>
<li>Pinpoints memory leaks from target hardware to source code lines.</li>
<li>Discovers resource leaks from process.</li>
<li>Command line interface and Carbide.c++ Extension.</li>
</ul>
<h3><a name="newfeatures"></a>What's new</h3>
<ul>
<li>Feature: Support added for new trace format.</li>
<li>Feature: New output formats added: Output to trace and Output to file
system.</li>
<li>Feature: Tread ID is shown in Properties for all allocations,
deallocations and leaks.</li>
<li>Feature: Added Graph settings dialog for setting thresholds for
allocations shown in the graph view.</li>
<li>Feature: Real-time tracing re-factoring.</li>
<li>Feature: Version checks and notification dialogs added for the following:
for the old trace format containing the old PCSS prefix; for supported
trace format version; for supported command line engine and command line
engine availability; for unknown tags in traces; for mismatch between
AnalyzeTool binaries in the device and AnalyzeTool headers in the SDK.</li>
</ul>
<h3><a name="installation" id="installation"></a>Installation notes</h3>
<ul>
<li>Update details for version 1.10.0 here</li>
</ul>
<h3><a name="requirements"></a>System requirements</h3>
<p>Basic Requirements:</p>
<ul>
<li>Windows XP.</li>
<li>S60 5.x (R&D SW).</li>
<li>ARMV5 or GCCE compiler.</li>
<li>TraceViewer Carbide.c++ Extension (version 1.0.1+).</li>
</ul>
<p>Additional Requirements:</p>
<ul>
<li>TraceViewer connection is required for collecting real time data from
target hardware to PC.</li>
</ul>
<h3><a name="compissues"></a>Compatibility issues</h3>
<ul>
<li>Not compatible with versions 1.7.3 or older of AnalyzeTool (any
component).</li>
<li>AnalyzeTool iby files (ROM image creation) at S60 5.0 SDK and higher are
not compatible with older than week 16/2009 release of SDK.</li>
<li>Kernel code analysis not supported.</li>
</ul>
<h3><a name="issues"></a>Known issues</h3>
<ul>
<li><b>Note:</b> If you are updating AnalyzeTool from the version older than
1.5.0, AnalyzeTool uses a different folder structure compared to previous
versions. Therefore it is essential that you check that there are no header
files in the folder <i>\epoc32\include\applications\analyzetool</i> or
<i>\epoc32\include\analyzetool</i>.</li>
<li>Tested processes must be closed successfully, meaning that they cannot be
panicked or exited abnormally (will cause also a lot of false memory
leaks).</li>
<li>Handle leaks in subtest shows subtraction of open handles within the
subtest.</li>
<li>The subtesting feature cannot be used with internal data gathering
mode.</li>
<li>Memory leaks from ECOM plugins are reported, but not pinpointed to code
lines inside plugin.</li>
<li>Pinpointing memory leaks from urel binaries shows only function
names.</li>
</ul>
<h3>Version history</h3>
<h5>Version 1.9.0 - 21st April 2010</h5>
<ul>
<li>Feature: The version of the dbghelp.dll library provided by Windows is
checked when user starts tracing. If the version is not at least 6.3.0.0, a
confirmation dialog will appear with instructions on how to update a later
version. </li>
<li>Fix: Substantially reduced the graph memory usage in the callstack area.
This allowed removing the option for disabling the graph feature in the
Preferences page.</li>
<li>Fix: Cleaning dialog functionality has been fixed, the graph is no longer
cleaned if user selects <strong>No</strong>.</li>
<li>Fix: Warning "No project selected" is no longer mistakenly displayed if
the project is selected in Navigator.</li>
</ul>
<h5>Version 1.8.1 - 14th January 2010</h5>
<ul>
<li>Feature: Add linefeeds to CLE generated XML report</li>
<li>Fix: Support for hooking test components (abld).</li>
<li>Fix: Error reading raptor makefile(line lenght over 16k)</li>
<li>Fix: Data file saved to wrong location on C drive.</li>
<li>Fix: Graph pinpointing prevents further project builds.</li>
<li>Fix: Graph memory usage improvements and preferences page feature for
disabling graph features.</li>
<li>Fix: Configuration UI crashes if can't connect to storage server</li>
</ul>
<h5>Version 1.8.0 – 12th December 2009</h5>
<ul>
<li>Feature: Memory usage shown as graph.</li>
</ul>
<h5>Version 1.7.4 – 4th November 2009</h5>
<ul>
<li>Feature: Third data gathering mode which is simple and fast.</li>
<li>Feature: Support for specifying call stack size(s).</li>
<li>Feature: Button to open preferences.</li>
<li>Feature: New error dialogs in Carbide extension.</li>
<li>Feature: Extension version number shown in AnalyzeTool view.</li>
<li>Fix: Inform user in build phase that kernel mode is not
supported/hooked.</li>
<li>Fix: Version conflict not shown to user.</li>
<li>Fix: Selecting leak from sub test does not give call stack info.</li>
</ul>
<h5>Version 1.7.3 – 1st October 2009</h5>
<ul>
<li>Fix: Support for define multiple symbol files</li>
<li>Fix: Carbide extension builds project although the selected target is not
supported. </li>
</ul>
<h5>Version in 1.7.2 – 3th September 2009</h5>
<ul>
<li>Fix: Memory leak information copied to clipboard.</li>
</ul>
<h5>Version in 1.7.1 – 19th August 2009</h5>
<ul>
<li>Fix: Decrease extension memory usage when creating results.</li>
<li>Fix: Device data file input should not accept path.</li>
</ul>
<h5>Version in 1.7.0 – 25th June 2009</h5>
<ul>
<li>Feature: "-debug" passed as build argument in Carbide.</li>
<li>Feature: Carbide.c++ AnalyzeTool building of a QT project.</li>
<li>Feature: Refresh button which makes results again.</li>
<li>Feature: AnalyzeTool Carbide.c++ Extension can be used to visualize
results for emulator/simulator memory leaks automatically.</li>
<li>Fix: Improve parsing speed of addresses.</li>
<li>Fix: Verbose output renders AnalyzeTool unusable slow.</li>
<li>Fix: Usability Improvement: Console view should be opened after building
done.</li>
</ul>
<h5>Version in 1.6.0 – 20th April 2009</h5>
<ul>
<li>Feature: Rom symbol file can be defined in Carbide Extension
preferences.</li>
<li>Feature: AnalyzeTool memory leak results can be cleared from view.</li>
<li>Feature: Number of max callstack items increased to 40.</li>
<li>Feature: On the fly call stack filtering improved.</li>
<li>Feature: "PROCESS_END x ABNORMAL" are now printed also when internal data
gathering mode is used.</li>
<li>Feature: Supports for pinpointing codelines from GCCE binaries.</li>
<li>Feature: Pinpoint memory leaks to code lines also in urel builds.</li>
<li>Feature: Cheat sheet for AnalyzeTool created.</li>
<li>Feature: Carbide extension checks atool.exe version before using it.</li>
<li>Feature: atool.exe version number showed in AnalyzeTool preference
page.</li>
<li>Feature: AnalyzeTool "core" version number is displayed in Carbide
preferences.</li>
<li>Feature: Added support for pinpointing codelines from static libraries in
ARMV5 platform.</li>
<li>Fix: Pinpointing works also to dlls in emulator environment.</li>
<li>Fix: Clear AnalyzeTool changes runs reallyclean also.</li>
<li>Fix: Error message is displayed when user analysis invalid data.</li>
<li>Fix: Cancelling build enabled during pre-builder.</li>
<li>Fix: Analysis progress bar now progresses.</li>
</ul>
<h5>Version in 1.5.2 – 27th March 2009</h5>
<ul>
<li>Feature: AnalyzeTool to work also in emulator.</li>
<li>Feature: AnalyzeTool Carbide extension can be used without Traceviewer
Extension.</li>
<li>Fix: Running atool -c in directory where only empty atool_temp directory
exists will not delete atool_temp directory.</li>
<li>Fix: In analyze report pinpointed memory </li>
<li>leak count is always zero when using sbs v.2, in logging levels 1 &
2.</li>
<li>Fix: Use of raptor build variables leads to incorrect listing file name
with certain types.</li>
<li>Fix: AnalyzeTool can share existing TraceViewer connection.</li>
<li>Fix: Unnecessary "Can not analyze" dialog is no longer displayed after
the project is built with AnalyzeTool.</li>
<li>Fix: Needed files for AnalyzeTool hooking are also checked for
winscw.</li>
<li>Fix: Analyze Tool Pre- and Post-Build Errors are added to Problems
View.</li>
<li>Fix: AnalyzeTool debug logging improved.</li>
<li>Fix: Start tracing icon changed.</li>
<li>Fix: If SDK prefs not ok in Carbide, atool gives error: missing libraries
from SDK.</li>
<li>Fix: Crash when trying to navigate to source location.</li>
<li>Fix: Emulator pinpoints to wrong cpp file.</li>
<li>Fix: Progress monitor is shown while starting the TraceViewer
connection.</li>
<li>Fix: Command line tool, "atool.exe", is bundled into the Carbide
extension.</li>
<li>Fix: unnecessary copying of trace file removed from Carbide.</li>
<li>Fix: Disable unnecessary AnalyzeTool buttons when trace is started.</li>
</ul>
<h5>Version 1.5.1 – 19th March 2009</h5>
<ul>
<li>Feature: Atool version is checked when hooked application is started.</li>
<li>Feature: Added support for pinpointing codelines from static libraries in
ARMV5 platform</li>
<li>Fix: Abnormal process ends not anymore showed for non-AnalyzeTool
processes.</li>
</ul>
<h5>Version 1.5.0 – 19th February 2009</h5>
<ul>
<li>Feature: AnalyzeTool to work also in emulator.</li>
<li>Feature: AnalyzeTool Carbide extension can be used without Traceviewer
Extension.</li>
<li>Fix: Running atool -c in directory where only empty atool_temp directory
exists will not delete atool_temp directory.</li>
<li>Fix: In analyze report pinpointed memory leak count is always zero when
using sbs v.2, in logging levels 1 & 2.</li>
<li>Fix: Use of raptor build variables leads to incorrect listing file name
with certain types.</li>
<li>Fix: AnalyzeTool can share existing TraceViewer connection.</li>
<li>Fix: Unnecessary "Can not analyze" dialog is no longer displayed after
the project is built with AnalyzeTool.</li>
<li>Fix: Needed files for AnalyzeTool hooking are also checked for
winscw.</li>
<li>Fix: Analyze Tool Pre- and Post-Build Errors are added to Problems
View.</li>
<li>Fix: AnalyzeTool debug logging improved.</li>
<li>Fix: Start tracing icon changed.</li>
<li>Fix: If SDK prefs not ok in Carbide, atool gives error: missing libraries
from SDK.</li>
<li>Fix: Crash when trying to navigate to source location.</li>
<li>Fix: Emulator pinpoints to wrong cpp file.</li>
<li>Fix: Progress monitor is shown while starting the TraceViewer
connection.</li>
<li>Fix: Command line tool, "atool.exe", is bundled into the Carbide
extension.</li>
<li>Fix: unnecessary copying of trace file removed from Carbide.</li>
<li>Fix: Disable unnecessary AnalyzeTool buttons when trace is started.</li>
</ul>
<h5>Version 1.4.1 – 19th December 2008</h5>
<ul>
<li>Change: Carbide Extension could show which modules are built with
atool.</li>
<li>Change: Atool supports Symbian build system version 2 (SBS v.2).</li>
<li>Change: Subtest memory analysis summary should be separated inside to
subtest information.</li>
<li>Change: Carbide extension to ask user "to continue or abort compilation"
if target is not supported.</li>
<li>Change: AnalyzeTool window buttons improvement.</li>
<li>Change: History of files opened added to open file button.</li>
<li>Change: Verbose configuration option for Carbide.c++.</li>
<li>Change: Results include processes udeb/urel info.</li>
<li>Fix: Carbide Extension cannot find the .cpp file where memoryleak is
pinpointed.</li>
<li>Fix: Usability Improvement: Preferences page and Logging mode.</li>
<li>Fix: Number of leaks in subtest is displayed in report.</li>
<li>Fix: Support analysing data files without /epoc32/build content or from
sub folder where build was made.</li>
<li>Fix: Atool will not show the correct name of subtest if it contains
spaces.</li>
<li>Fix: Compiling a project deletes logging data file from atool_temp.</li>
<li>Fix: Temporary file left to output directory in atool.exe analyze.</li>
<li>Fix: AnalyzeTool window not updated after current project change.</li>
<li>Fix: Number of memory leaks info should be updated after report detail
level change.</li>
<li>Fix: Project only specifies one MMP but all the MMP files are built.</li>
<li>Fix: Changing detail level of report clears call stack window.</li>
<li>Fix: AnalyzeTool post-builder is not working with variants on
Carbide.c++.</li>
<li>Fix: "Start Trace" clears results from all open projects.</li>
<li>Fix: Pinpointing from urel module does not work from Carbide.c++.</li>
</ul>
<h5>Version 1.4.0 – 12th December 2008</h5>
<ul>
<li>Change: History of files opened added to open file button.</li>
<li>Change: Verbose configuration option for Carbide.c++.</li>
<li>Change: Results include processes udeb/urel info.</li>
<li>Fix: Project only specifies one MMP but all the mmp files are built.</li>
<li>Fix: Changing detail level of report clears callstack window.</li>
<li>Fix: AnalyzeTool post-builder is not working with variants on
Carbide.c++.</li>
<li>Fix: "Start Trace" clears results from all open projects.</li>
<li>Fix: Pinpointing from urel module does not work from Carbide.</li>
</ul>
<h5>Version 1.3.3 – 27th November 2008</h5>
<ul>
<li>Change: History of files opened added to open file button.</li>
<li>Change: Verbose configuration option for Carbide.c++.</li>
<li>Change: Results include processes udeb/urel info.</li>
<li>Fix: Project only specifies one MMP but all the mmp files are built.</li>
<li>Fix: Changing detail level of report clears callstack window.</li>
<li>Fix: AnalyzeTool post-builder is not working with variants on
Carbide.c++.</li>
<li>Fix: "Start Trace" clears results from all open projects.</li>
<li>Fix: Pinpointing from urel module does not work from Carbide.</li>
</ul>
<h5>Version 1.3.2 – 13th November 2008</h5>
<ul>
<li>Change: History of files opened added to open file button.</li>
<li>Change: Verbose configuration option for Carbide.c++.</li>
<li>Change: Results include processes udeb/urel info.</li>
<li>Fix: Project only specifies one MMP but all the mmp files are built.</li>
<li>Fix: Changing detail level of report clears callstack window.</li>
<li>Fix: AnalyzeTool post-builder is not working with variants on
Carbide.c++.</li>
<li>Fix: "Start Trace" clears results from all open projects.</li>
<li>Fix: Pinpointing from urel module does not work from Carbide.</li>
</ul>
<h5>Version 1.3.1 – 30th October 2008</h5>
<ul>
<li>Change: - A single process start - end, should not be a test run.</li>
<li>Change: Carbide.c++ Extension shows ABNORMAL text when system exception
happens in the phone.</li>
<li>Change: Carbide.c++ Extension could filter memory leaks which does not
contain any call stack.</li>
<li>Change: MemoryHook reports PROCESS_END with ABNORMAL tag.</li>
<li>Change: atool -c to undo mmp change.</li>
<li>Change: Modules with read only mmp files can be hooked.</li>
<li>Change: Print S60 logging filename if not given.</li>
<li>Fix: Multiple subtests within test run show only one subtest.</li>
<li>Fix: Logging levels 1 and 3 produce same results when using UREL
target.</li>
<li>Fix: Memoryhook prints PROCESS_END when child threads are killed.</li>
<li>Fix: Atool reports runs from irrelevant PROCESS_ENDS.</li>
<li>Fix: No error message data file can not be opened.</li>
<li>Fix: NPE when using the Analyze View in Carbide 2.0.</li>
<li>Fix: "Error 1 make[1]: *** Waiting for unfinished jobs...." error is
displayed during the AnalyzeTool build.</li>
<li>Fix: run abld reallyclean instead of abld clean.</li>
<li>Fix: AnalyzeTool builder "is shown active" after importing a deleted
project again to Carbide.c++.</li>
<li>Fix: Progress information: Executing AnalyzeTool, Cannot send to
background.</li>
<li>Fix: Devlon52 or other ARMV5 based variants cannot be built from
Carbide.</li>
</ul>
<h5>Version 1.3.0 – 23rd October 2008</h5>
<ul>
<li>Change: A single process start - end, should not be a test run.</li>
<li>Change: Carbide.c++ Extension shows ABNORMAL text when system exception
happens in the phone.</li>
<li>Change: Carbide.c++ Extension could filter memory leaks which does not
contain any call stack.</li>
<li>Change: MemoryHook reports PROCESS_END with ABNORMAL tag.</li>
<li>Change: atool -c to undo mmp change.</li>
<li>Change: Modules with read only mmp files can be hooked.</li>
<li>Change: Print S60 logging filename if not given.</li>
<li>Fix: Multiple subtests within test run show only one subtest.</li>
<li>Fix: Logging levels 1 and 3 produce same results when using UREL
target.</li>
<li>Fix: Memoryhook prints PROCESS_END when child threads are killed.</li>
<li>Fix: Atool reports runs from irrelevant PROCESS_ENDS.</li>
<li>Fix: No error message data file can not be opened.</li>
<li>Fix: NPE when using the Analyze View in Carbide 2.0.</li>
</ul>
<h5>Version 1.2.1 – 2nd October 2008</h5>
<ul>
<li>Change: AnalyzeTool building method changed: AnalyzeTool Carbide.c++
Extension uses now the Carbide builder.</li>
</ul>
<h5>Version 1.2.0 – 18th September 2008</h5>
<ul>
<li>Change: AnalyzeTool building method changed: AnalyzeTool Carbide.c++
Extension uses now the Carbide builder.</li>
</ul>
<h5>Version 1.1.2 – 21th August 2008</h5>
<ul>
<li>Fix: Launching Carbide.c++ generates error message to the atool error
log.</li>
<li>Fix: 'Module not build with AnalyzeTool' is still displayed after
AnalyzeTool build.</li>
</ul>
<h5>Version 1.1.1 – 7th August 2008</h5>
<ul>
<li>Fix: Command line tool can not handle project where two MMP-files are in
same directory.</li>
</ul>
<h5>Version 1.1.0 – 10th July 2008</h5>
<ul>
<li>Feature: Trace data can be saved to a file.</li>
<li>Feature: Cancel logging from ConfigUI feature.</li>
<li>Fix: Redundant handle leak information.</li>
</ul>
<h5>Version 1.0.0 – 7th July 2008</h5>
<p>The first version.</p>
<div id="footer">
Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies).<br>
All rights reserved. <br>
This component and the accompanying materials are made available <br>
under the terms of "Eclipse Public License v1.0" <br>
which accompanies this distribution and is available <br>
at the URL <a
href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.
<br>
<br>
Initial Contributors:<br>
Nokia Corporation - initial contribution <br>
<br>
Contributors:<br>
Description: </div>
</body>
</html>