There are two alternative ways to capture data, depending on the output mode.
Note! AnalyzeTool decides which connection method to use by checking the project active build configuration settings. If the active build configuration is set to WINSCW, AnalyzeTool captures data from the emulator output file (%tmp%\epocwind.out); in ARMV5 and GCEE build configurations AnalyzeTool captures data using the tracing utility connection.
Note! This option requires that a tracing utility is available and a connection is established to the target hardware.
USB tracing can not be run from the device bootup because it requires USB tracing activation from the device side.
To capture data:
NOTE that at this point the system checks the version of the dbghelp.dll library provided by Windows. 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.
Now AnalyzeTool has captured data, saved it into the project's bld.inf\atool_temp directory, and the memory analysis results are displayed in the AnalyzeTool view.
When you select the output to file system mode in AnalyzeTool build, AnalyzeTool collects the test data into a file.
Note! If you are analyzing an application in the target hardware, the file must be transferred to a PC after the test run is completed.
To capture data:
NOTE The name of the file and the location where the file is saved in the target hardware are defined in the AnalyzeTool preferences.
In the emulator environment the file is saved in \epoc32\winscw\c\logs\analyzetool\.