Release note
AnalyzeTool Carbide.c++ Extension – Version 1.8.0
Released 12th December 2009
Product description
AnalyzeTool is a test software tool that is used for testing Symbian software for memory leaks and pinpointing the leaking problems in the source code.
For any support email list "D-AnalyzeTool-Support DG" should be used.
Main features
- UI for activating a memory leak analysis.
- UI for seeing results of a memory leak analysis.
- Pinpoints memory leaks from target hardware to source code lines.
- Discovers resource leaks from process.
- Command line interface and Carbide.c++ Extension.
What's new
Installation notes
System requirements
Basic Requirements:
- Windows XP.
- S60 3.1, 3.2, 5.0 or 5.1 (R&D SW).
- ARMV5 or GCCE compiler.
- Tracing utility Carbide.c++ Extension (version 1.0.1+).
Additional Requirements:
- Tracing utility connection (USB connection) is required for collecting real time data from target hardware to PC.
Compatibility issues
- 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.
- Not compatible with older versions than 1.6.0 of AnalyzeTool command line engine.
- Kernel code analysis not supported.
Known issues
- Note: 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 \epoc32\include\applications\analyzetool or \epoc32\include\analyzetool.
- Tested processes must be closed successfully, meaning that they cannot be panicked or exited abnormally (will cause also a lot of false memory leaks).
- Handle leaks in subtest shows substraction of open handles within the subtest.
- The subtesting feature cannot be used with internal data gathering mode.
- Memory leaks from ECOM plugins are reported, but not pinpointed to code lines inside plugin.
- Pinpointing memory leaks from urel binaries shows only function names.
Version history
Version 1.7.4 – 4th November 2009
- Feature: [AT-560] - Third data gathering mode which is simple and fast.
- Feature: [AT-592] - Support for specifying call stack size(s).
- Feature: [AT-627] - Button to open preferences.
- Feature: [AT-551] - New error dialogs in Carbide extension.
- Feature: [AT-583] - Extension version number shown in AnalyzeTool view.
- Fix: [AT-568] - Inform user in build phase that kernel mode is not supported/hooked.
- Fix: [AT-623] - Version conflict not shown to user.
- Fix: [AT-632] - Selecting leak from sub test does not give call stack info.
Version 1.7.3 – 1st October 2009
- Fix: [AT-570] - Support for define multiple symbol files
- Fix: [AT-586] - Carbide extension builds project although the selected target is not supported.
Version in 1.7.2 – 3th September 2009
- Fix: [AT-538] - Memory leak information copied to clipboard.
Version in 1.7.1 – 19th August 2009
- Fix: [AT-542] - Decrease extension memory usage when creating results.
- Fix: [AT-553] - Device data file input should not accept path.
Version in 1.7.0 – 25th June 2009
- Feature: [AT-520] - "-debug" passed as build argument in Carbide.
- Feature: [AT-134] - Carbide.c++ AnalyzeTool building of a QT project.
- Feature: [AT-236] - Refresh button which makes results again.
- Feature: [AT-136] - AnalyzeTool Carbide.c++ Extension can be used to visualize results for emulator/simulator memory leaks automatically.
- Fix: [AT-517] - Improve parsing speed of addresses.
- Fix: [AT-464] - Verbose output renders AnalyzeTool unusable slow.
- Fix: [AT-279] - Usability Improvement: Console view should be opened after building done.
Version in 1.6.0 – 20th April 2009
- Feature: [AT-480] - Rom symbol file can be defined in Carbide Extension preferences.
- Feature: [AT-489] - AnalyzeTool memory leak results can be cleared from view.
- Feature: [AT-475] - Number of max callstack items increased to 40.
- Feature: [AT-453] - On the fly call stack filtering improved.
- Feature: [AT-481] - "PROCESS_END x ABNORMAL" are now printed also when internal data gathering mode is used.
- Feature: [AT-337] - Supports for pinpointing codelines from GCCE binaries.
- Feature: [AT-113] - Pinpoint memory leaks to code lines also in urel builds.
- Feature: [AT-467] - Cheat sheet for AnalyzeTool created.
- Feature: [AT-416] - Carbide extension checks atool.exe version before using it.
- Feature: [AT-440] - atool.exe version number showed in AnalyzeTool preference page.
- Feature: [AT-442] - AnalyzeTool "core" version number is displayed in Carbide preferences.
- Feature: [AT-451] - Added support for pinpointing codelines from static libraries in ARMV5 platform.
- Fix: [AT-461] - Pinpointing works also to dlls in emulator environment.
- Fix: [AT-419] - Clear AnalyzeTool changes runs reallyclean also.
- Fix: [AT-446] - Error message is displayed when user analysis invalid data.
- Fix: [AT-466] - Cancelling build enabled during pre-builder.
- Fix: [AT-420] - Analysis progress bar now progresses.
Version in 1.5.2 – 27th March 2009
- Feature: [AT-254] - AnalyzeTool to work also in emulator.
- Feature: [AT-323] - AnalyzeTool Carbide extension can be used without Traceviewer Extension.
- Fix: [AT-350] - Running atool -c in directory where only empty atool_temp directory exists will not delete atool_temp directory.
- Fix: [AT-330] - In analyze report pinpointed memoryleak count is always zero when using sbs v.2, in logging levels 1 & 2.
- Fix: [AT-333] - Use of raptor build variables leads to incorrect listing file name with certain types.
- Fix: [AT-357] - AnalyzeTool can share existing Tracing utility connection.
- Fix: [AT-361] - Unnecessary "Can not analyze" dialog is no longer displayed after the project is built with AnalyzeTool.
- Fix: [AT-363] - Needed files for AnalyzeTool hooking are also checked for winscw.
- Fix: [AT-376] - Analyze Tool Pre- and Post-Build Errors are added to Problems View.
- Fix: [AT-272] - AnalyzeTool debug logging improved.
- Fix: [AT-374] - Start tracing icon changed.
- Fix: [AT-372] - If SDK prefs not ok in Carbide, atool gives error: missing libraries from SDK.
- Fix: [AT-378] - Crash when trying to navigate to source location.
- Fix: [AT-390] - Emulator pinpoints to wrong cpp file.
- Fix: [AT-393] - Progress monitor is shown while starting the Tracing utility connection.
- Fix: [AT-410] - Command line tool, "atool.exe", is bundled into the Carbide extension.
- Fix: [AT-325] - unnecessary copying of trace file removed from Carbide.
- Fix: [AT-358] - Disable unnecessary AnalyzeTool buttons when trace is started.
Version 1.5.1 – 19th March 2009
- Feature: [AT-443] - Atool version is checked when hooked application is started.
- Fearure: [AT-451] - Added support for pinpointing codelines from static libraries in ARMV5 platform.
- Fix: [AT-422] - Abnormal process ends not anymore showed for non-AnalyzeTool processes.
Version 1.5.0 – 19th February 2009
- Feature: [AT-254] - AnalyzeTool to work also in emulator.
- Feature: [AT-323] - AnalyzeTool Carbide extension can be used without Traceviewer Extension.
- Fix: [AT-350] - Running atool -c in directory where only empty atool_temp directory exists will not delete atool_temp directory.
- Fix: [AT-330] - In analyze report pinpointed memoryleak count is always zero when using sbs v.2, in logging levels 1 & 2.
- Fix: [AT-333] - Use of raptor build variables leads to incorrect listing file name with certain types.
- Fix: [AT-357] - AnalyzeTool can share existing Tracing utility connection.
- Fix: [AT-361] - Unnecessary "Can not analyze" dialog is no longer displayed after the project is built with AnalyzeTool.
- Fix: [AT-363] - Needed files for AnalyzeTool hooking are also checked for winscw.
- Fix: [AT-376] - Analyze Tool Pre- and Post-Build Errors are added to Problems View.
- Fix: [AT-272] - AnalyzeTool debug logging improved.
- Fix: [AT-374] - Start tracing icon changed.
- Fix: [AT-372] - If SDK prefs not ok in Carbide, atool gives error: missing libraries from SDK.
- Fix: [AT-378] - Crash when trying to navigate to source location.
- Fix: [AT-390] - Emulator pinpoints to wrong cpp file.
- Fix: [AT-393] - Progress monitor is shown while starting the Tracing utility connection.
- Fix: [AT-410] - Command line tool, "atool.exe", is bundled into the Carbide extension.
- Fix: [AT-325] - unnecessary copying of trace file removed from Carbide.
- Fix: [AT-358] - Disable unnecessary AnalyzeTool buttons when trace is started.
Version 1.4.1 – 19th December 2008
- Change: [AT-235] - Carbide Extension could show which modules are built with atool.
- Change: [AT-263] - Atool supports Symbian build system version 2 (SBS v.2).
- Change: [AT-69] - Subtest memory analysis summary should be separated inside to subtest information.
- Change: [AT-252] - Carbide extension to ask user "to continue or abort compilation" if target is not supported.
- Change: [AT-274] - AnalyzeTool window buttons improvement.
- Change: [AT-218] - History of files opened added to open file button.
- Change: [AT-219] - Verbose configuration option for Carbide.c++.
- Change: [AT-233] - Results include processes udeb/urel info.
- Fix: [AT-205] - Carbide Extension cannot find the .cpp file where memoryleak is pinpointed.
- Fix: [AT-278] - Usability Improvement: Preferences page and Logging mode.
- Fix: [AT-300] - Number of leaks in subtest is displayed in report.
- Fix: [AT-237] - Support analysing datafiles without /epoc32/build content or from sub folder where build was made.
- Fix: [AT-276] - Atool will not show the correct name of subtest if it contains spaces.
- Fix: [AT-280] - Compiling a project deletes logging data file from atool_temp.
- Fix: [AT-285] - Temporary file left to output directory in atool.exe analyze.
- Fix: [AT-286] - AnalyzeTool window not updated after current project change.
- Fix: [AT-289] - Number of memory leaks info should be updated after report detail level change.
- Fix: [AT-226] - Project only specifies one MMP but all the MMP files are built.
- Fix: [AT-234] - Changing detail level of report clears call stack window.
- Fix: [AT-249] - AnalyzeTool post-builder is not working with variants on Carbide.c++.
- Fix: [AT-273] - "Start Trace" clears results from all open projects.
- Fix: [AT-275] - Pinpointing from urel module does not work from Carbide.c++.
Version 1.4.0 – 12th December 2008
- Change: [AT-218] - History of files opened added to open file button.
- Change: [AT-219] - Verbose configuration option for Carbide.c++.
- Change: [AT-233] - Results include processes udeb/urel info.
- Fix: [AT-226] - Project only specifies one MMP but all the mmp files are built.
- Fix: [AT-234] - Changing detail level of report clears callstack window.
- Fix: [AT-249] - AnalyzeTool post-builder is not working with variants on Carbide.c++.
- Fix: [AT-273] - "Start Trace" clears results from all open projects.
- Fix: [AT-275] - Pinpointing from urel module does not work from Carbide.
Version 1.3.3 – 27th November 2008
- Change: [AT-218] - History of files opened added to open file button.
- Change: [AT-219] - Verbose configuration option for Carbide.c++.
- Change: [AT-233] - Results include processes udeb/urel info.
- Fix: [AT-226] - Project only specifies one MMP but all the mmp files are built.
- Fix: [AT-234] - Changing detail level of report clears callstack window.
- Fix: [AT-249] - AnalyzeTool post-builder is not working with variants on Carbide.c++.
- Fix: [AT-273] - "Start Trace" clears results from all open projects.
- Fix: [AT-275] - Pinpointing from urel module does not work from Carbide.
Version 1.3.2 – 13th November 2008
- Change: [AT-218] - History of files opened added to open file button.
- Change: [AT-219] - Verbose configuration option for Carbide.c++.
- Change: [AT-233] - Results include processes udeb/urel info.
- Fix: [AT-226] - Project only specifies one MMP but all the mmp files are built.
- Fix: [AT-234] - Changing detail level of report clears callstack window.
- Fix: [AT-249] - AnalyzeTool post-builder is not working with variants on Carbide.c++.
- Fix: [AT-273] - "Start Trace" clears results from all open projects.
- Fix: [AT-275] - Pinpointing from urel module does not work from Carbide.
Version 1.3.1 – 30th October 2008
- Change: [AT-163] - A single process start - end, should not be a test run.
- Change: [AT-189] - Carbide.c++ Extension shows ABNORMAL text when system exception happens in the phone.
- Change: [AT-190] - Carbide.c++ Extension could filter memory leaks which does not contain any call stack.
- Change: [AT-191] - MemoryHook reports PROCESS_END with ABNORMAL tag.
- Change: [AT-192] - atool -c to undo mmp change.
- Change: [AT-202] - Modules with read only mmp files can be hooked.
- Change: [AT-209] - Print S60 logging filename if not given.
- Fix: [AT-156] - Multiple subtests within test run show only one subtest.
- Fix: [AT-181] - Logging levels 1 and 3 produce same results when using UREL target.
- Fix: [AT-204] - Memoryhook prints PROCESS_END when child threads are killed.
- Fix: [AT-206] - Atool reports runs from irrelevant PROCESS_ENDS.
- Fix: [AT-222] - No error message data file can not be opened.
- Fix: [AT-225] - NPE when using the Analyze View in Carbide 2.0.
- Fix: [AT-243] - "Error 1 make[1]: *** Waiting for unfinished jobs...." error is displayed during the AnalyzeTool build.
- Fix: [AT-247] - run abld reallyclean instead of abld clean.
- Fix: [AT-248] - AnalyzeTool builder "is shown active" after importing a deleted project again to Carbide.c++.
- Fix: [AT-212] - Progress information: Executing AnalyzeTool, Cannot send to background.
- Fix: [AT-250] - Devlon52 or other ARMV5 based variants cannot be built from Carbide.
Version 1.3.0 – 23rd October 2008
- Change: [AT-163] - A single process start - end, should not be a test run.
- Change: [AT-189] - Carbide.c++ Extension shows ABNORMAL text when system exception happens in the phone.
- Change: [AT-190] - Carbide.c++ Extension could filter memory leaks which does not contain any call stack.
- Change: [AT-191] - MemoryHook reports PROCESS_END with ABNORMAL tag.
- Change: [AT-192] - atool -c to undo mmp change.
- Change: [AT-202] - Modules with read only mmp files can be hooked.
- Change: [AT-209] - Print S60 logging filename if not given.
- Fix: [AT-156] - Multiple subtests within test run show only one subtest.
- Fix: [AT-181] - Logging levels 1 and 3 produce same results when using UREL target.
- Fix: [AT-204] - Memoryhook prints PROCESS_END when child threads are killed.
- Fix: [AT-206] - Atool reports runs from irrelevant PROCESS_ENDS.
- Fix: [AT-222] - No error message data file can not be opened.
- Fix: [AT-225] - NPE when using the Analyze View in Carbide 2.0.
Version 1.2.1 – 2nd October 2008
- Change: AnalyzeTool building method changed: AnalyzeTool Carbide.c++ Extension uses now the Carbide builder.
Version 1.2.0 – 18th September 2008
- Change: AnalyzeTool building method changed: AnalyzeTool Carbide.c++ Extension uses now the Carbide builder.
Version 1.1.2 – 21th August 2008
- Fix: [AT-97] - Launching Carbide.c++ generates error message to the atool error log.
- Fix: [AT-99] - 'Module not build with AnalyzeTool' is still displayed after AnalyzeTool build.
Version 1.1.1 – 7th August 2008
- Fix: [AT-72] - Command line tool can not handle project where two MMP-files are in same directory.
Version 1.1.0 – 10th July 2008
- Feature: [AT-59] - Trace data can be saved to a file.
- Feature: [AT-68] - Cancel logging from ConfigUI feature.
- Fix: [AT-70] - Redundant handle leak information.
Version 1.0.0 – 7th July 2008
The first version.