diff -r bb339882c6e9 -r 0367d2db2c06 sysperfana/analyzetoolext/com.nokia.s60tools.analyzetool.help/html/tasks/capture.htm --- a/sysperfana/analyzetoolext/com.nokia.s60tools.analyzetool.help/html/tasks/capture.htm Tue Aug 24 12:10:03 2010 +0300 +++ b/sysperfana/analyzetoolext/com.nokia.s60tools.analyzetool.help/html/tasks/capture.htm Tue Aug 24 12:16:27 2010 +0300 @@ -10,11 +10,10 @@

Capturing data

-

There are two alternative ways to capture data, depending on the data -gathering mode.

+

There are two alternative ways to capture data, depending on the output +mode.

-

Capturing data in monitored external or external data -gathering mode

+

Capturing data in output to trace mode

Note! AnalyzeTool decides which connection method to use by checking the project active build configuration settings. If the active build @@ -36,10 +35,10 @@ 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.

    +

    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 @@ -53,11 +52,10 @@
    • -

    Capturing data in monitored internal data gathering -mode

    +

    Capturing data in output to file system mode

    -

    When you select the monitored internal data gathering mode in -AnalyzeTool build, AnalyzeTool collects the test data into a file.

    +

    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.

    @@ -71,11 +69,12 @@
  • 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.

    + will write the test data to a file. +

    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\.

  • While the tested software project is active in the Project Explorer, open the data file by clicking Open and analyze data