The following table lists AnalyzeTool error messages:
+ +| Message | +Description | +
|---|---|
| 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. | +
| 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:
+ +| Problem | +Possible 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.
+ +| Error | +Possible 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 SDK | +Your build environment is missing the necessary files for building with AnalyzeTool. You need to compile AnalyzeTool to all platforms in your environment. | +
| 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. | +