diff -r bb339882c6e9 -r 0367d2db2c06 sysperfana/analyzetoolext/com.nokia.s60tools.analyzetool.help/html/reference/troubleshooting.htm --- a/sysperfana/analyzetoolext/com.nokia.s60tools.analyzetool.help/html/reference/troubleshooting.htm Tue Aug 24 12:10:03 2010 +0300 +++ b/sysperfana/analyzetoolext/com.nokia.s60tools.analyzetool.help/html/reference/troubleshooting.htm Tue Aug 24 12:16:27 2010 +0300 @@ -1,131 +1,324 @@ - - - - - -AnalyzeTool Troubleshooting - - - - -

Troubleshooting

-

The following table lists AnalyzeTool error messages:

- - --- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MessageDescription
No project selected. Please select project.You tried to use Carbide.c++ Extension actions but you have not selected a project first. Select a project from the Project Explorer window, and run action again.
Could not find mmp file for current project.AnalyzeTool Carbide.c++ Extension could not load the mmp file info. Ensure that project's bld.inf file contains mmp files.
TraceViewer connection reserved for another plug-in.Another Carbide.c++ Extension uses TraceViewer. First close the other TraceViewer Carbide.c++ Extension connection, and then try again.
Invalid TraceViewer connection settings.The TraceViewer has invalid connection settings and could not connect to target hardware. Check the TraceViewer options from Window > Preferences... > Carbide Extensions > TraceViewer > Connection.
General TraceViewer error.The TraceViewer cannot connect to target hardware and the AnalyzeTool Carbide.c++ Extension could not resolve the problem. Check the TraceViewer options from Window > Preferences... > Carbide Extensions > TraceViewer > Connection.
Invalid name. Do you want to specify a valid name?You have entered an invalid subtest name, for example the name is empty or starts with an illegal parameter.
No process started, could not start a subtest.The trace is active but no processes started in the target hardware which are built with the external data gathering mode of AnalyzeTool.
The given subtest is already started for the active process.You have already started the subtest with same name for selected process. -
Cannot find AnalyzeTool libraries from current SDK. Install libraries first.This message is displayed in the Console view if AnalyzeTool is not included in SDK.
- -

The following table lists possible known problematic situations related to AnalyzeTool:

- - --- - - - - - - - - - - - - - - - - - - - - - - - - - - -
ProblemPossible cause
Compiling with AnalyzeTool gives an error related to header files.Mixing header files from different AnalyzeTool versions might be the cause. From version 1.5.0 onwards, AnalyzeTool uses a different folder structure compared to previous versions. Therefore it is essential that you check that there are no header files in the folder \epoc32\include\applications\analyzetool or \epoc32\include\analyzetool.
Compiling with AnalyzeTool gives an error related to AnalyzeTool library files.Build environment is missing AnalyzeTool files. Install the AnalyzeTool to build environment by unzipping environment changes from AnalyzeTool installation folder..
Software compiled with AnalyzeTool does not run.Mixing header files from different AnalyzeTool versions might be the cause. From version 1.5.0 onwards, AnalyzeTool uses a different folder structure compared to previous versions. Therefore it is essential that you check that there are no header files in the folder \epoc32\include\applications\analyzetool or \epoc32\include\analyzetool.
Software compiled with AnalyzeTool does not run.AnalyzeTool core components are missing from the target HW/emulator environment.
Software compiled with AnalyzeTool does not run.The AnalyzeTool core components in the target HW/emulator environment are old (incompatible) versions.
- -

The following ones are Command line engine related errors. These errors are displayed in the Carbide.c++ Console view.

- - --- - - - - - - - - - - - - - - - - - - - - - - -
ErrorPossible cause
Mmp file: <mmp file name> is read only. Compile aborted.The project's mmp file is read only. Remove the write protection from the mmp file.
AnalyzeTool build failed in module: <mmp file name>.Project contains build errors. Details can be found from Console view.
Can not find AnalyzeTool libraries from current SDKYour build environment is missing the necessary files for building with AnalyzeTool. These files can be found from the AnalyzeTool installation folder from files S60_environment_changes31.zip, S60_environment_changes32.zip or S60_environment_changes50.zip. Unzip one of these to the desired Symbian OS root directory. The zip-package itself includes the necessary subfolder structure.
AnalyzeTool : Errors :
-Missing symbol file:
You are using GCCE release build which does not produce needed symbol files. Symbol files are needed to pinpoint memory leaks. To correct this user needs to add "-debug" to project's build configuration arguments. To do this open project's properties, select Carbide.c++ > Build Configurations > Arguments while the GCCE release build configuration is selected and write the -debug to arguments field.
- - - - \ No newline at end of file + + + + + + AnalyzeTool Troubleshooting + + + + +

Troubleshooting

+ +

The following table lists AnalyzeTool error messages:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MessageDescription
Cannot find AnalyzeTool libraries from current SDK. Install libraries + first.This message is displayed in the Console view if AnalyzeTool + is not included in SDK.
Can not find AnalyzeTool library files from current SDK: + +

<list of libraries that are missing>

+ +

You can build AnalyzeTool from sources or contact AnalyzeTool + development team to get AnalyzeTool binaries.

+
This message appears during compiling if there are some SDK library + files missing. + +

To resolve the problem, build AnalyzeTool from sources or contact + AnalyzeTool development team for AnalyzeTool binaries.

+
Could not find mmp file for current project.AnalyzeTool Carbide.c++ Extension could not load the mmp file info. + Ensure that project's bld.inf file contains mmp files.
Command Line Engine older than x.x.x.This message is displayed in the Preferences window if the version of + the selected command line engine is earlier than the version of the + Carbide extension (for example 1.10.0). + +

To resolve the problem, unless you already have the version listed + in the error message available, you must update the command line engine + to the listed version, When you have the correct version available, + select/browse to that version in the preferences page.

+
Command Line Engine not availableThis message appears, when the Preferences page is opened, if the + command line engine is not available in the selected path location. + +

To resolve the problem, set the correct location for the command + line engine in the AnalyzeTool Engine section of the Preferences page. + Or, if there is no AnalyzeTool Engine available, you must install + one.

+
General TraceViewer error.The TraceViewer cannot connect to target hardware and the AnalyzeTool + Carbide.c++ Extension could not resolve the problem. Check the + TraceViewer options from Window > Preferences... > Carbide + Extensions > TraceViewer > Connection.
Invalid name. Do you want to specify a valid name?You have entered an invalid subtest name, for example the name is + empty or starts with an illegal parameter.
Invalid TraceViewer connection settings.The TraceViewer has invalid connection settings and could not connect + to target hardware. Check the TraceViewer options from Window > + Preferences... > Carbide Extensions > TraceViewer > + Connection.
No process started, could not start a subtest.The trace is active but no processes started in the target hardware + which are built with the output to trace mode of AnalyzeTool.
No project selected. Please select project.You tried to use Carbide.c++ Extension actions but you have not + selected a project first. Select a project from the Project + Explorer window, and run action again.
The given subtest is already started for the active process.You have already started the subtest with same name for selected + process.
TraceViewer connection reserved for another plug-in.Another Carbide.c++ Extension uses TraceViewer. First close the other + TraceViewer Carbide.c++ Extension connection, and then try again.
Unknown tag + +

Trace contains unknown xxx tag. AnalyzeTool Carbide extension might + not be up to date.

+
This warning is shown during online tracing or when you open a data + file that contains trace data with unknown tags. + +

The warning is shown again for each unknown tag encountered. You you + do not wish to see the warning again, you can check the Don't + show again checkbox.

+ +

To resolve the problem, you should update AnalyzeTool Carbide + extension to the latest available version.

+
Unsupported format + +

Carbide extension is older than Symbian components. Please see Help + for more information.

+
This message appears during online tracing or when you try to open a + data file that includes traces in a format that is not supported by the + version of AnalyzeTool extension you are using. + +

To resolve the problem, you should update AnalyzeTool Carbide + extension to the latest available version.

+
Unsupported format + +

Symbian components are not up to date. Please see Help for more + information.

+
This message appears during online tracing or when you try to open a + log file that includes traces in old trace format. From version 1.10.0 + onwards, the AnalyzeTool Carbide.c++ extension supports the new trace + format, so the S60 component running on the device must be version + 1.10.0 or higher. + +

To resolve the problem, you should update the AnalyzeTool Symbian + component on your device to the latest available version.

+
Version mismatch + +

Command Line engine not available. Check AnalyzeTool preferences.

+
This message appears, when starting a build, if the command line + engine is not available in the path location selected in the + AnalyzeTool preferences. + +

To resolve the problem:

+
    +
  1. Open AnalyzeTool Preferences by clicking iconicon.
  2. +
  3. In the Analyze Tool Engine section, select / browse to the + correct version of the command line engine, or
  4. +
  5. If you do not have the correct version of the command line + engine, you must install it.
  6. +
+
Version mismatch + +

Command Line engine older than x.x.x. Check AnalyzeTool + preferences.

+
This message is displayed when starting a build, if the version of + the command line engine selected in the Preference page is earlier than + the version of the Carbide extension (for example 1.10.0). + +

To resolve the problem:

+
    +
  1. Open AnalyzeTool Preferences by clicking iconicon.
  2. +
  3. In the Analyze Tool Engine section, select / browse to the + correct version of the command line engine, or
  4. +
  5. If you do not have the correct version of the command line + engine, you must install it.
  6. +
+
Version Mismatch + +

Version mismatch between the AnalyzeTool binaries (version x.y.z) in + the device and AnalyzeTool headers in the SDK (x.y.z).

+ +

Please make surethat those match otherwise results may be + unknown.

+
This warning message can appear during online tracing, or when + opening data file, if the versions of the Carbide extension and S60 + application do not match. + +

To avoid problems, use the same version on Carbide extension and S60 + component, otherwise results may be inaccurate.

+
+ +

The following table lists possible known problematic situations related to +AnalyzeTool:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ProblemPossible cause
Compiling with AnalyzeTool gives an error related to header + files.Mixing header files from different AnalyzeTool versions might be the + cause. From version 1.5.0 onwards, AnalyzeTool uses a different folder + structure compared to previous versions. Therefore it is essential that + you check that there are no header files in the folder + \epoc32\include\applications\analyzetool or + \epoc32\include\analyzetool.
Compiling with AnalyzeTool gives an error related to AnalyzeTool + library files.Build environment is missing AnalyzeTool files. Install the + AnalyzeTool to build environment by unzipping environment changes from + AnalyzeTool installation folder..
Software compiled with AnalyzeTool does not run.Mixing header files from different AnalyzeTool versions might be the + cause. From version 1.5.0 onwards, AnalyzeTool uses a different folder + structure compared to previous versions. Therefore it is essential that + you check that there are no header files in the folder + \epoc32\include\applications\analyzetool or + \epoc32\include\analyzetool.
Software compiled with AnalyzeTool does not run.AnalyzeTool core components are missing from the target HW/emulator + environment.
Software compiled with AnalyzeTool does not run.The AnalyzeTool core components in the target HW/emulator environment + are old (incompatible) versions.
+ +

The following ones are Command line engine related errors. These errors are +displayed in the Carbide.c++ Console view.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
ErrorPossible cause
Mmp file: <mmp file name> is read only. Compile aborted.The project's mmp file is read only. Remove the write protection from + the mmp file.
AnalyzeTool build failed in module: <mmp file name>.Project contains build errors. Details can be found from + Console view.
Can not find AnalyzeTool libraries from current SDKYour build environment is missing the necessary files for building + with AnalyzeTool. These files can be found from the AnalyzeTool + installation folder from files S60_environment_changes31.zip, + S60_environment_changes32.zip or S60_environment_changes50.zip. Unzip + one of these to the desired Symbian OS root directory. The zip-package + itself includes the necessary sub-folder structure.
AnalyzeTool : Errors :
+ Missing symbol file: < symbol file name>
You are using GCCE release build which does not produce needed symbol + files. Symbol files are needed to pinpoint memory leaks. To correct + this user needs to add "-debug" to project's build configuration + arguments. To do this open project's properties, select + Carbide.c++ > Build Configurations > Arguments while the + GCCE release build configuration is selected and write the + -debug to arguments field.
+ + + +