Capturing data
There are two alternative ways to capture data, depending on the data
gathering mode.
Capturing data in monitored external or external data
gathering 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:
- Open the AnalyzeTool view (if it is not already open) by selecting
Window > Show View > Other... > Carbide Extensions >
AnalyzeTool.
- Start capturing data by clicking Start tracing in the AnalyzeTool
toolbar.
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.
- Start the application built with AnalyzeTool, and run the desired test
cases. Note that Carbide.c++ needs to be connected to the target
hardware.
- At the end of a test run, close the tested application (process). After
you have closed the application, stop the test run by clicking Stop
tracing.
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.
Capturing data in monitored internal data gathering
mode
When you select the monitored internal data gathering 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:
- Install the AnalyzeTool software to the target hardware if not already
installed.
- Install the test software built with AnalyzeTool to the target
hardware.
- Start the application built with AnalyzeTool in the target hardware, and
run the desired test cases.
- At the end of a test run, close the tested application (process). This
will write the test data to a file. In the target hardware the file is
saved in e:\analyzetool\ or c:\data\analyzetool\ depending if
the memory card is used or not. In the emulator environment the file is
saved in \epoc32\winscw\c\logs\analyzetool\.
Note! The data file name was specified before the build.
- While the tested software project is active in the Project
Explorer, open the data file by clicking Open and analyze data
file in the AnalyzeTool toolbar. This will run the analysis and
display the results in the AnalyzeTool view.