diff -r 844b047e260d -r f65f740e69f9 sysperfana/analyzetoolext/com.nokia.s60tools.analyzetool.help/html/concepts/preferences.htm --- a/sysperfana/analyzetoolext/com.nokia.s60tools.analyzetool.help/html/concepts/preferences.htm Wed Apr 21 15:14:16 2010 +0300 +++ b/sysperfana/analyzetoolext/com.nokia.s60tools.analyzetool.help/html/concepts/preferences.htm Wed Apr 21 19:42:48 2010 +0300 @@ -1,92 +1,119 @@ - - - - - -AnalyzeTool preferences - - - - -

AnalyzeTool preferences

-

You can change the AnalyzeTool preferences by selecting Window > Preferences...> Carbide Extensions > AnalyzeTool.

-

Setting preferences

-

The AnalyzeTool preferences are described in the following table:

- --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OptionsDescription
AnalyzeTool EngineAnalyzeTool uses the command line utility atool.exe which is used for instrumenting and uninstrumenting the project and analysing captured data. -
    -
  • -Use internal engine. This option uses the built-in version of atool.exe. -
  • -
  • -Use external command line engine. This options uses atool.exe from a user-defined location. -
  • -
      -
    -
Verbose outputEnables command line engine debug information to the Console view.
Engine versionDisplays selected engine version number.
Data gathering modeSpecifies the data gathering mode for AnalyzeTool build. -
    -
  • Monitored External or External: This option will send the memory analysis data through tracing utility connection. For more information, see Capturing data in external data gathering mode.
  • -
  • Internal: This option will create a data file to the target hardware. The data file name is the same as the project name. If you select the Name from the user option, you must define a name for the data file. For more information, see Capturing data in internal data gathering mode -
      -
    • Name from the process: This option will a use data file name which is the same as application target name.
    • -
    • Name from the user: This option will ask a data file name every time a project is built with the atool.exe.
    • -
    -
  • -
  • Ask always: This option will ask before each build which data gathering mode to use, External or Internal
  • -
Stored callstack size -
    -
  • No items. This option does not store any callstack items.
  • -
  • 40 items. This option stores forty callstack items.
  • -
  • 100 items. This option stores hundred callstack items
  • -
  • Custom callstack size. This option provides possibility to define custom size of callstack items. Custom size of callstack items is limited to 0-255
  • - -
-Note! The callstack size affects the speed of hooked process, lower callstack size is faster. -
Report levelSpecifies the report level of memory leak analysis results. -
    -
  • Show every detail: This option displays all the call stack information.
  • -
  • Show only known code lines: This option displays all the known line numbers of call stack information.
  • -
  • Show only topmost memory allocation code line: This option displays the first known line of call stack information.
  • -
- - - - + + + + + + AnalyzeTool preferences + + + + +

AnalyzeTool preferences

+ +

You can change the AnalyzeTool preferences by selecting Window > +Preferences...> Carbide Extensions > AnalyzeTool.

+ +

Setting preferences

+ +

The AnalyzeTool preferences are described in the following table:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
OptionsDescription
AnalyzeTool EngineAnalyzeTool uses the command line utility atool.exe which is + used for instrumenting and uninstrumenting the project and analysing + captured data. +
    +
  • Use internal engine. This option uses the built-in version of + atool.exe.
  • +
  • Use external command line engine. This options uses + atool.exe from a user-defined location. +
      +
    +
  • +
+
Verbose outputEnables command line engine debug information to the Console + view.
Engine versionDisplays selected engine version number.
Data gathering modeSpecifies the data gathering mode for AnalyzeTool build. +
    +
  • Monitored External or External: This option will send the memory + analysis data through tracing utility connection. For more + information, see Capturing data in + external data gathering mode.
  • +
  • Internal: This option will create a data file to the target + hardware. The data file name is the same as the project name. If + you select the Name from the user option, you must define a + name for the data file. For more information, see Capturing data in + internal data gathering mode +
      +
    • Name from the process: This option will a use data file name + which is the same as application target name.
    • +
    • Name from the user: This option will ask a data file name + every time a project is built with the atool.exe.
    • +
    +
  • +
  • Ask always: This option will ask before each build which data + gathering mode to use, External or Internal
  • +
+
Stored callstack size
    +
  • No items. This option does not store any callstack items.
  • +
  • 40 items. This option stores forty callstack items.
  • +
  • 100 items. This option stores hundred callstack items
  • +
  • Custom callstack size. This option provides possibility to define + custom size of callstack items. Custom size of callstack items is + limited to 0-255
  • +
+ Note! The callstack size affects the speed of hooked process, + lower callstack size is faster.
Report levelSpecifies the report level of memory leak analysis results. +
    +
  • Show every detail: This option displays all the call stack + information.
  • +
  • Show only known code lines: This option displays all the known + line numbers of call stack information.
  • +
  • Show only topmost memory allocation code line: This option + displays the first known line of call stack information.
  • +
+
+ + + +