1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 1.0 Transitional//EN"> |
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 1.0 Transitional//EN"> |
2 <html> |
2 <html> |
3 <head> |
3 <head> |
4 <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> |
4 <meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> |
5 <meta http-equiv="content-style-type" content="text/css"> |
5 <meta http-equiv="content-style-type" content="text/css"> |
6 <title>AnalyzeTool Troubleshooting</title> |
6 <title>AnalyzeTool Troubleshooting</title> |
7 <link href="../../book.css" type="text/css" rel="StyleSheet"> |
7 <link href="../../book.css" type="text/css" rel="StyleSheet"> |
8 </head> |
8 </head> |
|
9 |
9 <body> |
10 <body> |
10 |
|
11 <h2>Troubleshooting</h2> |
11 <h2>Troubleshooting</h2> |
|
12 |
12 <p>The following table lists AnalyzeTool error messages:</p> |
13 <p>The following table lists AnalyzeTool error messages:</p> |
13 |
14 |
14 <table width="615" border="1" cellspacing="1" cellpadding="2"> |
15 <table width="615" border="1" cellspacing="1" cellpadding="2"> |
15 <colgroup> |
16 <colgroup><col width="250*"> |
16 <col width="250*"> |
17 <col width="356*"> |
17 <col width="356*"></colgroup> |
18 </colgroup> |
18 <tbody> |
19 <tbody> |
19 <tr> |
20 <tr> |
20 <th>Message</th> |
21 <th>Message</th> |
21 <th align="center">Description</th> |
22 <th align="center">Description</th> |
22 </tr> |
23 </tr> |
23 <tr> |
24 <tr> |
24 <td>No project selected. Please select project.</td> |
25 <td>Cannot find AnalyzeTool libraries from current SDK. Install libraries |
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 first.</td> |
26 </tr> |
27 <td>This message is displayed in the <b>Console</b> view if AnalyzeTool |
27 <tr> |
28 is not included in SDK.</td> |
28 <td>Could not find mmp file for current project.</td> |
29 </tr> |
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> |
30 </tr> |
31 <td>Can not find AnalyzeTool library files from current SDK: |
31 <tr> |
32 |
32 <td>TraceViewer connection reserved for another plug-in.</td> |
33 <p><list of libraries that are missing></p> |
33 <td>Another Carbide.c++ Extension uses TraceViewer. First close the other TraceViewer Carbide.c++ Extension connection, and then try again.</td> |
34 |
34 </tr> |
35 <p>You can build AnalyzeTool from sources or contact AnalyzeTool |
35 <tr> |
36 development team to get AnalyzeTool binaries.</p> |
36 <td>Invalid TraceViewer connection settings.</td> |
37 </td> |
37 <td>The TraceViewer has invalid connection settings and could not connect to target hardware. Check the TraceViewer options from <b>Window > Preferences... > Carbide Extensions > TraceViewer > Connection</b>.</td> |
38 <td>This message appears during compiling if there are some SDK library |
38 </tr> |
39 files missing. |
39 <tr> |
40 |
40 <td>General TraceViewer error.</td> |
41 <p>To resolve the problem, build AnalyzeTool from sources or contact |
41 <td>The TraceViewer cannot connect to target hardware and the AnalyzeTool Carbide.c++ Extension could not resolve the problem. Check the TraceViewer options from <b>Window > Preferences... > Carbide Extensions > TraceViewer > Connection</b>.</td> |
42 AnalyzeTool development team for AnalyzeTool binaries.</p> |
42 </tr> |
43 </td> |
43 <tr> |
44 </tr> |
44 <td>Invalid name. Do you want to specify a valid name?</td> |
45 <tr> |
45 <td>You have entered an invalid subtest name, for example the name is empty or starts with an illegal parameter.</td> |
46 <td>Could not find mmp file for current project.</td> |
46 </tr> |
47 <td>AnalyzeTool Carbide.c++ Extension could not load the mmp file info. |
47 <tr> |
48 Ensure that project's <i>bld.inf</i> file contains mmp files.</td> |
48 <td>No process started, could not start a subtest.</td> |
49 </tr> |
49 <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> |
50 <tr> |
50 </tr> |
51 <td>Command Line Engine older than x.x.x.</td> |
51 <tr> |
52 <td>This message is displayed in the Preferences window if the version of |
52 <td>The given subtest is already started for the active process.</td> |
53 the selected command line engine is earlier than the version of the |
53 <td>You have already started the subtest with same name for selected process. |
54 Carbide extension (for example 1.10.0). |
54 </td> |
55 |
55 </tr> |
56 <p>To resolve the problem, unless you already have the version listed |
56 <tr> |
57 in the error message available, you must update the command line engine |
57 <td>Cannot find AnalyzeTool libraries from current SDK. Install libraries first.</td> |
58 to the listed version, When you have the correct version available, |
58 <td>This message is displayed in the <b>Console</b> view if AnalyzeTool is not included in SDK.</td> |
59 select/browse to that version in the preferences page. </p> |
59 </tr> |
60 </td> |
60 </tbody> |
61 </tr> |
|
62 <tr> |
|
63 <td>Command Line Engine not available</td> |
|
64 <td>This message appears, when the Preferences page is opened, if the |
|
65 command line engine is not available in the selected path location. |
|
66 |
|
67 <p>To resolve the problem, set the correct location for the command |
|
68 line engine in the AnalyzeTool Engine section of the Preferences page. |
|
69 Or, if there is no AnalyzeTool Engine available, you must install |
|
70 one.</p> |
|
71 </td> |
|
72 </tr> |
|
73 <tr> |
|
74 <td>General TraceViewer error.</td> |
|
75 <td>The TraceViewer cannot connect to target hardware and the AnalyzeTool |
|
76 Carbide.c++ Extension could not resolve the problem. Check the |
|
77 TraceViewer options from <b>Window > Preferences... > Carbide |
|
78 Extensions > TraceViewer > Connection</b>.</td> |
|
79 </tr> |
|
80 <tr> |
|
81 <td>Invalid name. Do you want to specify a valid name?</td> |
|
82 <td>You have entered an invalid subtest name, for example the name is |
|
83 empty or starts with an illegal parameter.</td> |
|
84 </tr> |
|
85 <tr> |
|
86 <td>Invalid TraceViewer connection settings.</td> |
|
87 <td>The TraceViewer has invalid connection settings and could not connect |
|
88 to target hardware. Check the TraceViewer options from <b>Window > |
|
89 Preferences... > Carbide Extensions > TraceViewer > |
|
90 Connection</b>.</td> |
|
91 </tr> |
|
92 <tr> |
|
93 <td>No process started, could not start a subtest.</td> |
|
94 <td>The trace is active but no processes started in the target hardware |
|
95 which are built with the output to trace mode of AnalyzeTool.</td> |
|
96 </tr> |
|
97 <tr> |
|
98 <td>No project selected. Please select project.</td> |
|
99 <td>You tried to use Carbide.c++ Extension actions but you have not |
|
100 selected a project first. Select a project from the <b>Project |
|
101 Explorer</b> window, and run action again.</td> |
|
102 </tr> |
|
103 <tr> |
|
104 <td>The given subtest is already started for the active process.</td> |
|
105 <td>You have already started the subtest with same name for selected |
|
106 process. </td> |
|
107 </tr> |
|
108 <tr> |
|
109 <td>TraceViewer connection reserved for another plug-in.</td> |
|
110 <td>Another Carbide.c++ Extension uses TraceViewer. First close the other |
|
111 TraceViewer Carbide.c++ Extension connection, and then try again.</td> |
|
112 </tr> |
|
113 <tr> |
|
114 <td>Unknown tag |
|
115 |
|
116 <p>Trace contains unknown xxx tag. AnalyzeTool Carbide extension might |
|
117 not be up to date.</p> |
|
118 </td> |
|
119 <td>This warning is shown during online tracing or when you open a data |
|
120 file that contains trace data with unknown tags. |
|
121 |
|
122 <p>The warning is shown again for each unknown tag encountered. You you |
|
123 do not wish to see the warning again, you can check the <strong>Don't |
|
124 show again</strong> checkbox.</p> |
|
125 |
|
126 <p>To resolve the problem, you should update AnalyzeTool Carbide |
|
127 extension to the latest available version.</p> |
|
128 </td> |
|
129 </tr> |
|
130 <tr> |
|
131 <td>Unsupported format |
|
132 |
|
133 <p>Carbide extension is older than Symbian components. Please see Help |
|
134 for more information.</p> |
|
135 </td> |
|
136 <td>This message appears during online tracing or when you try to open a |
|
137 data file that includes traces in a format that is not supported by the |
|
138 version of AnalyzeTool extension you are using. |
|
139 |
|
140 <p>To resolve the problem, you should update AnalyzeTool Carbide |
|
141 extension to the latest available version. </p> |
|
142 </td> |
|
143 </tr> |
|
144 <tr> |
|
145 <td>Unsupported format |
|
146 |
|
147 <p>Symbian components are not up to date. Please see Help for more |
|
148 information.</p> |
|
149 </td> |
|
150 <td>This message appears during online tracing or when you try to open a |
|
151 log file that includes traces in old trace format. From version 1.10.0 |
|
152 onwards, the AnalyzeTool Carbide.c++ extension supports the new trace |
|
153 format, so the S60 component running on the device must be version |
|
154 1.10.0 or higher. |
|
155 |
|
156 <p>To resolve the problem, you should update the AnalyzeTool Symbian |
|
157 component on your device to the latest available version.</p> |
|
158 </td> |
|
159 </tr> |
|
160 <tr> |
|
161 <td>Version mismatch |
|
162 |
|
163 <p>Command Line engine not available. Check AnalyzeTool preferences.</p> |
|
164 </td> |
|
165 <td>This message appears, when starting a build, if the command line |
|
166 engine is not available in the path location selected in the |
|
167 AnalyzeTool preferences. |
|
168 |
|
169 <p>To resolve the problem:</p> |
|
170 <ol> |
|
171 <li>Open AnalyzeTool Preferences by clicking <img alt="icon" |
|
172 src="../images/btn_preferences.png" width="16" |
|
173 height="16">icon.</li> |
|
174 <li>In the Analyze Tool Engine section, select / browse to the |
|
175 correct version of the command line engine, or</li> |
|
176 <li>If you do not have the correct version of the command line |
|
177 engine, you must install it.</li> |
|
178 </ol> |
|
179 </td> |
|
180 </tr> |
|
181 <tr> |
|
182 <td>Version mismatch |
|
183 |
|
184 <p>Command Line engine older than x.x.x. Check AnalyzeTool |
|
185 preferences.</p> |
|
186 </td> |
|
187 <td>This message is displayed when starting a build, if the version of |
|
188 the command line engine selected in the Preference page is earlier than |
|
189 the version of the Carbide extension (for example 1.10.0). |
|
190 |
|
191 <p>To resolve the problem:</p> |
|
192 <ol> |
|
193 <li>Open AnalyzeTool Preferences by clicking <img alt="icon" |
|
194 src="../images/btn_preferences.png" width="16" |
|
195 height="16">icon.</li> |
|
196 <li>In the Analyze Tool Engine section, select / browse to the |
|
197 correct version of the command line engine, or</li> |
|
198 <li>If you do not have the correct version of the command line |
|
199 engine, you must install it.</li> |
|
200 </ol> |
|
201 </td> |
|
202 </tr> |
|
203 <tr> |
|
204 <td>Version Mismatch |
|
205 |
|
206 <p>Version mismatch between the AnalyzeTool binaries (version x.y.z) in |
|
207 the device and AnalyzeTool headers in the SDK (x.y.z).</p> |
|
208 |
|
209 <p>Please make surethat those match otherwise results may be |
|
210 unknown.</p> |
|
211 </td> |
|
212 <td>This warning message can appear during online tracing, or when |
|
213 opening data file, if the versions of the Carbide extension and S60 |
|
214 application do not match. |
|
215 |
|
216 <p>To avoid problems, use the same version on Carbide extension and S60 |
|
217 component, otherwise results may be inaccurate.</p> |
|
218 </td> |
|
219 </tr> |
|
220 </tbody> |
61 </table> |
221 </table> |
62 |
222 |
63 <p>The following table lists possible known problematic situations related to AnalyzeTool:</p> |
223 <p>The following table lists possible known problematic situations related to |
|
224 AnalyzeTool:</p> |
64 |
225 |
65 <table width="615" border="1" cellspacing="1" cellpadding="2"> |
226 <table width="615" border="1" cellspacing="1" cellpadding="2"> |
66 <colgroup> |
227 <colgroup><col width="250*"> |
67 <col width="250*"> |
228 <col width="356*"> |
68 <col width="356*"></colgroup> |
229 </colgroup> |
69 <tbody> |
230 <tbody> |
70 <tr> |
231 <tr> |
71 <th>Problem</th> |
232 <th>Problem</th> |
72 <th align="center">Possible cause</th> |
233 <th align="center">Possible cause</th> |
73 </tr> |
234 </tr> |
74 <tr> |
235 <tr> |
75 <td>Compiling with AnalyzeTool gives an error related to header files.</td> |
236 <td>Compiling with AnalyzeTool gives an error related to header |
76 <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> |
237 files.</td> |
77 </tr> |
238 <td>Mixing header files from different AnalyzeTool versions might be the |
78 <tr> |
239 cause. From version 1.5.0 onwards, AnalyzeTool uses a different folder |
79 <td>Compiling with AnalyzeTool gives an error related to AnalyzeTool library files.</td> |
240 structure compared to previous versions. Therefore it is essential that |
80 <td>Build environment is missing AnalyzeTool files. Install the AnalyzeTool to build environment by unzipping environment changes from AnalyzeTool installation folder.</i>.</td> |
241 you check that there are no header files in the folder |
81 </tr> |
242 <i>\epoc32\include\applications\analyzetool</i> or |
82 <tr> |
243 <i>\epoc32\include\analyzetool</i>.</td> |
83 <td>Software compiled with AnalyzeTool does not run.</td> |
244 </tr> |
84 <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> |
245 <tr> |
85 </tr> |
246 <td>Compiling with AnalyzeTool gives an error related to AnalyzeTool |
86 <tr> |
247 library files.</td> |
87 <td>Software compiled with AnalyzeTool does not run.</td> |
248 <td>Build environment is missing AnalyzeTool files. Install the |
88 <td>AnalyzeTool core components are missing from the target HW/emulator environment.</td> |
249 AnalyzeTool to build environment by unzipping environment changes from |
89 </tr> |
250 AnalyzeTool installation folder..</td> |
90 <tr> |
251 </tr> |
91 <td>Software compiled with AnalyzeTool does not run.</td> |
252 <tr> |
92 <td>The AnalyzeTool core components in the target HW/emulator environment are old (incompatible) versions.</td> |
253 <td>Software compiled with AnalyzeTool does not run.</td> |
93 </tr> |
254 <td>Mixing header files from different AnalyzeTool versions might be the |
94 </tbody> |
255 cause. From version 1.5.0 onwards, AnalyzeTool uses a different folder |
|
256 structure compared to previous versions. Therefore it is essential that |
|
257 you check that there are no header files in the folder |
|
258 <i>\epoc32\include\applications\analyzetool</i> or |
|
259 <i>\epoc32\include\analyzetool</i>.</td> |
|
260 </tr> |
|
261 <tr> |
|
262 <td>Software compiled with AnalyzeTool does not run.</td> |
|
263 <td>AnalyzeTool core components are missing from the target HW/emulator |
|
264 environment.</td> |
|
265 </tr> |
|
266 <tr> |
|
267 <td>Software compiled with AnalyzeTool does not run.</td> |
|
268 <td>The AnalyzeTool core components in the target HW/emulator environment |
|
269 are old (incompatible) versions.</td> |
|
270 </tr> |
|
271 </tbody> |
95 </table> |
272 </table> |
96 |
273 |
97 <p>The following ones are Command line engine related errors. These errors are displayed in the Carbide.c++ <b>Console</b> view.</p> |
274 <p>The following ones are Command line engine related errors. These errors are |
|
275 displayed in the Carbide.c++ <b>Console</b> view.</p> |
98 |
276 |
99 <table> |
277 <table> |
100 <colgroup> |
278 <colgroup><col width="250*"> |
101 <col width="250*"> |
279 <col width="356*"> |
102 <col width="356*"></colgroup> |
280 </colgroup> |
103 <tbody> |
281 <tbody> |
104 <tr> |
282 <tr> |
105 <th>Error</th> |
283 <th>Error</th> |
106 <th align="center">Possible cause</th> |
284 <th align="center">Possible cause</th> |
107 </tr> |
285 </tr> |
108 <tr> |
286 <tr> |
109 <td>Mmp file: <mmp file name> is read only. Compile aborted.</td> |
287 <td>Mmp file: <mmp file name> is read only. Compile aborted.</td> |
110 <td>The project's mmp file is read only. Remove the write protection from the mmp file.</td> |
288 <td>The project's mmp file is read only. Remove the write protection from |
111 </tr> |
289 the mmp file.</td> |
112 <tr> |
290 </tr> |
113 <td>AnalyzeTool build failed in module: <mmp file name>.</td> |
291 <tr> |
114 <td>Project contains build errors. Details can be found from <b>Console</b> view.</td> |
292 <td>AnalyzeTool build failed in module: <mmp file name>.</td> |
115 </tr> |
293 <td>Project contains build errors. Details can be found from |
116 <tr> |
294 <b>Console</b> view.</td> |
117 <td>Can not find AnalyzeTool libraries from current SDK</td> |
295 </tr> |
118 <td>Your 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.</td> |
296 <tr> |
119 </tr> |
297 <td>Can not find AnalyzeTool libraries from current SDK</td> |
120 <tr> |
298 <td>Your build environment is missing the necessary files for building |
121 <td>AnalyzeTool : Errors :<br> |
299 with AnalyzeTool. These files can be found from the AnalyzeTool |
122 Missing symbol file: <symbol file name></td> |
300 installation folder from files S60_environment_changes31.zip, |
123 <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> |
301 S60_environment_changes32.zip or S60_environment_changes50.zip. Unzip |
124 </tr> |
302 one of these to the desired Symbian OS root directory. The zip-package |
125 </tbody> |
303 itself includes the necessary sub-folder structure.</td> |
|
304 </tr> |
|
305 <tr> |
|
306 <td>AnalyzeTool : Errors :<br> |
|
307 Missing symbol file: < symbol file name></td> |
|
308 <td>You are using GCCE release build which does not produce needed symbol |
|
309 files. Symbol files are needed to pinpoint memory leaks. To correct |
|
310 this user needs to add "<i>-debug</i>" to project's build configuration |
|
311 arguments. To do this open project's <b>properties</b>, select |
|
312 <b>Carbide.c++ > Build Configurations > Arguments</b> while the |
|
313 GCCE release build configuration is selected and write the |
|
314 <i>-debug</i> to arguments field.</td> |
|
315 </tr> |
|
316 </tbody> |
126 </table> |
317 </table> |
127 |
318 |
128 <div id="footer">Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. |
319 <div id="footer"> |
129 License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.</div> |
320 Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights |
|
321 reserved. License: <a |
|
322 href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.</div> |
130 </body> |
323 </body> |
131 </html> |
324 </html> |