diff -r bb339882c6e9 -r 0367d2db2c06 sysperfana/analyzetoolext/com.nokia.s60tools.analyzetool.help/html/gettingstarted/basic.htm --- a/sysperfana/analyzetoolext/com.nokia.s60tools.analyzetool.help/html/gettingstarted/basic.htm Tue Aug 24 12:10:03 2010 +0300 +++ b/sysperfana/analyzetoolext/com.nokia.s60tools.analyzetool.help/html/gettingstarted/basic.htm Tue Aug 24 12:16:27 2010 +0300 @@ -1,31 +1,46 @@ - - - - -AnalyzeTool Basic walk-through - - - - -

Basic walk-through

-

This section guides you with three easy steps for using AnalyzeTool to perform memory leak tests for a simple application.

-

You can launch the AnalyzeTool Carbide.c++ Extension by selecting AnalyzeTool in the Carbide menu, or from Window > Show View > Other... > Carbide Extensions > AnalyzeTool.

- -
Before you start
- - -

By following these simple steps you can start using AnalyzeTool:

-
    -
  1. Build the project with AnalyzeTool.
    2. -
  2. Capture data in the monitored external or external data gathering mode.

    If you cannot use the tracing utility connection to the target hardware, you can use the monitored internal data gathering mode.

    3. -
  3. View memory leaks.
    4. -
  4. View memory activity graph.
    5. -
- - - - \ No newline at end of file + + + + + AnalyzeTool Basic walk-through + + + + +

Basic walk-through

+ +

This section guides you with three easy steps for using AnalyzeTool to +perform memory leak tests for a simple application.

+ +

You can launch the AnalyzeTool Carbide.c++ Extension by selecting +AnalyzeTool in the Carbide menu, or from Window > Show View +> Other... > Carbide Extensions > AnalyzeTool.

+ +
Before you start
+ + +

By following these simple steps you can start using AnalyzeTool:

+
    +
  1. Build the project with AnalyzeTool.
    2. +
  2. Capture data in output to + trace mode. +

    If you cannot use the tracing utility connection to the target hardware, + you can use the output to + file system mode.

    +
    3. +
  3. View memory leaks.
    4. +
  4. View memory activity + graph.
    5. +
+ + + +