1 ===============================================================================

     2 

     3 RELEASE NOTES - ANALYZETOOL v1.9.1

     4 RELEASED 29th April 2010

     5 

     6 SUPPORTS SYMBIAN^1+

     7 

     8 ===============================================================================

     9 

    10 Product Description:

    11 ====================

    12 AnalyzeTool is a dynamic test tool that is used for testing Symbian software

    13 for memory and resource leaks and pinpointing the leaks from the source code.

    14 

    15 Main Features:

    16 ==============

    17 - Pinpoints memoryleaks from target hardware and emulator to source code lines

    18 - Discovers resource leaks from processes

    19 - Command line interface and Carbide.c++ Extension

    20 

    21 ===============================================================================

    22 

    23 What's New in v1.9.1

    24 ====================

    25 - Change: Removed Avkon and Console UI's to simplify the maintenance of the

    26   tool

    27 - Change: Middleware layer dependencies removed so AnalyzeTool can be now used

    28   also in OS layer builds

    29 - Fix: Move all binaries to ROM instead of ROFS to avoid ROM build

    30   dependencies issues in hooked components

    31 

    32 ===============================================================================

    33 

    34 Installation Notes:

    35 ===================

    36 AnalyzeTool is typically preinstalled on ROM. If not, it can be added to the

    37 ROM with the .iby file. Alternatively, the .sis file can be found under the sis-

    38 directory, but the user need to sign it with their own developer certificate.

    39 In Nokia R&D environment, you can use directly the R&D-signed .sis file under the

    40 internal\sis directory.

    41 

    42 When signing with own developer certificate, the following capabilities are

    43 needed:

    44   ReadDeviceData

    45   WriteDeviceData

    46   DiskAdmin

    47   AllFiles

    48   SwEvent

    49   NetworkServices

    50   LocalServices

    51   ReadUserData

    52   WriteUserData

    53   Location

    54   UserEnvironment

    55   CommDD

    56   PowerMgmt

    57   MultimediaDD

    58   DRM

    59   TrustedUI

    60   ProtServ

    61   NetworkControl

    62   SurroundingsDD

    63   TCB

    64 

    65 When builing AnalyzeTool against S60 3.0 or 3.1, you may need to patch your SDK

    66 environment first with some fixes. For more information, please refer to the

    67 instructions under the "envpatcher" directory.

    68 

    69 ===============================================================================

    70 

    71 System Requirements:

    72 ====================

    73 Basic Requirements:

    74 - Any S60 3.x device or emulator environment

    75 

    76 ===============================================================================

    77 

    78 Compatibility Issues:

    79 =====================

    80 N/A

    81 

    82 ===============================================================================

    83 

    84 Known Issues:

    85 =============

    86 - Kernel analysis are not supported.

    87 

    88 - When using monitored internal data gathering mode (-mi) and hooked

    89   application contains huge amounts of allocations AnalyzeTool? storageserver

    90   might run out of memory to store the data. This message "Symbian error code

    91   -4" is seen when analyzing the data file with atool.exe. Solution is to use

    92   external / monitored external data gathering mode. 

    93 

    94 - Switch allocator. AnalyzeTool change the application memory allocator to

    95   AnalyzeTool own memory allocator and using the User::SwitchAllocator function

    96   can lead to situation where the tested application does not work properly.

    97   

    98 - AnalyzeTool hooked QT applications becomes too slow to run. Use small size

    99   call stack(s) and new logging mode (external -e). 

   100 

   101 - Stif test case with AnalyzeTool can inform wrong memory leak alert.

   102 

   103 - AnalyzeTool overwrites functions TInt User::ProcessCritical(TCritical

   104   aCritical) and TInt User::SetProcessCritical(TCritical aCritical), but this

   105   works only when the function is called from hooked exe application. So if

   106   setting critical is done from DLL (even if it's hooked with AnalyzeTool) the

   107   overwriting does not work and the process stays set critical during the

   108   testing.

   109 

   110 - If hooked application is closed by calling User::Exit() from DLL instead of

   111   .exe application AnalyzeTool reports "abnormal process end" and can't report

   112   proper memory leaks.

   113  

   114 ===============================================================================

   115 

   116 Version History:

   117 ================

   118 

   119 Version 1.9.0 - 8th April 2010

   120 ==============================

   121 - Feature: Remove false positive memory leaks with better handling of global

   122   variables

   123 - Feature: Automatic check of correct version of dbghelp.dll for better

   124   emulator support

   125 - Change: HTI support removed

   126 - Fix: SBSVS variant compilation didn't work

   127 

   128 ===============================================================================

   129 

   130 Copyright (c) 2010 Nokia Corporation and/or its subsidiary(-ies).

   131 All rights reserved.

   132 

   133 This component and the accompanying materials are made available

   134 under the terms of "Eclipse Public License v1.0"

   135 which accompanies this distribution, and is available

   136 at the URL "http://www.eclipse.org/legal/epl-v10.html".