|
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 1.0 Transitional//EN"> |
|
2 <html> |
|
3 <head> |
|
4 <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> |
|
5 <meta http-equiv="content-style-type" content="text/css"> |
|
6 <title>AnalyzeTool Troubleshooting</title> |
|
7 <link href="../nokia.css" type="text/css" rel="StyleSheet"> |
|
8 </head> |
|
9 <body> |
|
10 |
|
11 <h2>Troubleshooting</h2> |
|
12 <p>The following table lists AnalyzeTool error messages:</p> |
|
13 |
|
14 <table width="615" border="1" cellspacing="1" cellpadding="2"> |
|
15 <colgroup> |
|
16 <col width="250*"> |
|
17 <col width="356*"></colgroup> |
|
18 <tbody> |
|
19 <tr> |
|
20 <th>Message</th> |
|
21 <th align="center">Description</th> |
|
22 </tr> |
|
23 <tr> |
|
24 <td>No project selected. Please select project.</td> |
|
25 <td>You tried to use Carbide.c++ Extension actions but you have not selected a project first. Select a project from the <b>Project Explorer</b> window, and run action again.</td> |
|
26 </tr> |
|
27 <tr> |
|
28 <td>Could not find mmp file for current project.</td> |
|
29 <td>AnalyzeTool Carbide.c++ Extension could not load the mmp file info. Ensure that project's <i>bld.inf</i> file contains mmp files.</td> |
|
30 </tr> |
|
31 <tr> |
|
32 <td>Invalid name. Do you want to specify a valid name?</td> |
|
33 <td>You have entered an invalid subtest name, for example the name is empty or starts with an illegal parameter.</td> |
|
34 </tr> |
|
35 <tr> |
|
36 <td>No process started, could not start a subtest.</td> |
|
37 <td>The trace is active but no processes started in the target hardware which are built with the external data gathering mode of AnalyzeTool.</td> |
|
38 </tr> |
|
39 <tr> |
|
40 <td>The given subtest is already started for the active process.</td> |
|
41 <td>You have already started the subtest with same name for selected process. |
|
42 </td> |
|
43 </tr> |
|
44 <tr> |
|
45 <td>Cannot find AnalyzeTool libraries from current SDK. Install libraries first.</td> |
|
46 <td>This message is displayed in the <b>Console</b> view if AnalyzeTool is not included in SDK.</td> |
|
47 </tr> |
|
48 </tbody> |
|
49 </table> |
|
50 |
|
51 <p>The following table lists possible known problematic situations related to AnalyzeTool:</p> |
|
52 |
|
53 <table width="615" border="1" cellspacing="1" cellpadding="2"> |
|
54 <colgroup> |
|
55 <col width="250*"> |
|
56 <col width="356*"></colgroup> |
|
57 <tbody> |
|
58 <tr> |
|
59 <th>Problem</th> |
|
60 <th align="center">Possible cause</th> |
|
61 </tr> |
|
62 <tr> |
|
63 <td>Compiling with AnalyzeTool gives an error related to header files.</td> |
|
64 <td>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 <i>\epoc32\include\applications\analyzetool</i> or <i>\epoc32\include\analyzetool</i>.</td> |
|
65 </tr> |
|
66 <tr> |
|
67 <td>Compiling with AnalyzeTool gives an error related to AnalyzeTool library files.</td> |
|
68 <td>Build environment is missing AnalyzeTool files. Install the AnalyzeTool to build environment by unzipping environment changes from AnalyzeTool installation folder.</i>.</td> |
|
69 </tr> |
|
70 <tr> |
|
71 <td>Software compiled with AnalyzeTool does not run.</td> |
|
72 <td>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 <i>\epoc32\include\applications\analyzetool</i> or <i>\epoc32\include\analyzetool</i>.</td> |
|
73 </tr> |
|
74 <tr> |
|
75 <td>Software compiled with AnalyzeTool does not run.</td> |
|
76 <td>AnalyzeTool core components are missing from the target HW/emulator environment.</td> |
|
77 </tr> |
|
78 <tr> |
|
79 <td>Software compiled with AnalyzeTool does not run.</td> |
|
80 <td>The AnalyzeTool core components in the target HW/emulator environment are old (incompatible) versions.</td> |
|
81 </tr> |
|
82 </tbody> |
|
83 </table> |
|
84 |
|
85 <p>The following ones are Command line engine related errors. These errors are displayed in the Carbide.c++ <b>Console</b> view.</p> |
|
86 |
|
87 <table> |
|
88 <colgroup> |
|
89 <col width="250*"> |
|
90 <col width="356*"></colgroup> |
|
91 <tbody> |
|
92 <tr> |
|
93 <th>Error</th> |
|
94 <th align="center">Possible cause</th> |
|
95 </tr> |
|
96 <tr> |
|
97 <td>Mmp file: <mmp file name> is read only. Compile aborted.</td> |
|
98 <td>The project's mmp file is read only. Remove the write protection from the mmp file.</td> |
|
99 </tr> |
|
100 <tr> |
|
101 <td>AnalyzeTool build failed in module: <mmp file name>.</td> |
|
102 <td>Project contains build errors. Details can be found from <b>Console</b> view.</td> |
|
103 </tr> |
|
104 <tr> |
|
105 <td>Can not find AnalyzeTool libraries from current SDK</td> |
|
106 <td>Your build environment is missing the necessary files for building with AnalyzeTool. You need to compile AnalyzeTool to all platforms in your environment.</td> |
|
107 </tr> |
|
108 <tr> |
|
109 <td>AnalyzeTool : Errors :<br> |
|
110 Missing symbol file: <symbol file name></td> |
|
111 <td>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 "<i>-debug</i>" to project's build configuration arguments. To do this open project's <b>properties</b>, select <b>Carbide.c++ > Build Configurations > Arguments</b> while the GCCE release build configuration is selected and write the <i>-debug</i> to arguments field.</td> |
|
112 </tr> |
|
113 </tbody> |
|
114 </table> |
|
115 |
|
116 <div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. |
|
117 License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.</div> |
|
118 </body> |
|
119 </html> |