|
2
|
1 |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
|
2 |
|
|
|
3 |
<html>
|
|
|
4 |
<head>
|
|
|
5 |
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
|
|
|
6 |
<title>Carbide.c++ Release Notes</title>
|
|
|
7 |
<link href="../book.css" rel="stylesheet" type="text/css" />
|
|
|
8 |
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
|
|
|
9 |
<link href="../book.css" rel="stylesheet" type="text/css" />
|
|
|
10 |
<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
|
|
|
11 |
<style type="text/css">
|
|
|
12 |
.style1 {font-family: "Courier New", Courier, mono}
|
|
|
13 |
.style5 {color: #FF0000}
|
|
|
14 |
.style6 {font-weight: bold}
|
|
|
15 |
.style8 {color: #000000; font-weight: bold; }
|
|
|
16 |
</style>
|
|
|
17 |
</head>
|
|
|
18 |
<body bgcolor="#ffffff">
|
|
|
19 |
<h2>Carbide.c++ Release Notes 2.0.3</h2>
|
|
|
20 |
<p>The Carbide.c++ is a comprehensive development tool suite for Symbian OS that is based on the Eclipse framework. The C++ Development Toolkit (CDT), provides the foundation for project and build tools management, as well as the primary interface for the debugger to communicate with the IDE. </p>
|
|
|
21 |
<p>This is a collection of important information concerning last-minute
|
|
|
22 |
changes and other topics that deserve special attention. Please
|
|
|
23 |
read these notes carefully before using the Carbide tools so you
|
|
|
24 |
understand the current limitations and workarounds for known
|
|
|
25 |
issues. </p>
|
|
|
26 |
<ul>
|
|
|
27 |
<li><a href="#whatsNew">What's new </a></li>
|
|
|
28 |
<li><a href="#beta">User notes</a></li>
|
|
|
29 |
<li><a href="bugs_fixed.htm">Fixed bugs</a> and <a href="#issues">workarounds</a></li>
|
|
|
30 |
<li><a href="#support">Technical support</a> </li>
|
|
|
31 |
</ul>
|
|
|
32 |
<p>Once you have read the release notes, we recommend you follow the <img src="images/command_link.png" width="16" height="12" alt="" /> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.cheatsheets.openCheatSheet(cheatSheetId=com.nokia.carbide.cpp.doc.user.getStarted)")'>HelloWorld tutorial</a> for
|
|
|
33 |
a quick introduction to Carbide.c++.</p>
|
|
|
34 |
<p class="note" style="color: rgb(255, 0, 0);"><span style="font-weight: bold;">WARNING</span>:
|
|
|
35 |
Updating the CDT feature in Carbide.c++/Eclipse will wipe out our
|
|
|
36 |
changes making the tools unusable!</p>
|
|
|
37 |
<p> See the <a href="hints_tips.htm">Tips & tricks</a> page for more helpful information.</p>
|
|
|
38 |
<h3><a name="whatsNew" id="whatsNew"></a>What's New in 2.0.3 </h3>
|
|
|
39 |
<p>The following features for Symbian OS development are provided within Carbide.c++:</p>
|
|
|
40 |
<ul>
|
|
|
41 |
<li><b>Carbide.c++ News Reader</b> - introducing the <a href="reference/view_carbide_news.htm">Carbide.c++ News</a> view which provides the latest Carbide, Symbian, and S60 news as well as news on tools updates and screencasts for Carbide development.</li>
|
|
|
42 |
</ul>
|
|
|
43 |
<h4>2.0.0</h4>
|
|
|
44 |
<ul><li><b>Eclipse 3.4.1 </b>— The Eclipse 3.4 project (Ganymede) provides the foundation, or integration platform, on which Carbide.c++ is built. See <a href="PLUGINS_ROOT/org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html">What's New in 3.4</a> for more information.</li>
|
|
|
45 |
</ul>
|
|
|
46 |
<ul><li><b>CDT 5.0.1</b> — The final version of CDT included as part of the Ganymede release. See the <a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew.htm">CDT 5.0 News and Noteworthy</a> page for more information. </li>
|
|
|
47 |
<li><b>SDK Migration support in CodeScanner</b> — CodeScanner now includes support for S60 SDK rules that provide helpful migration informaton on S60 functions within any C/C++ editor view and provide links to additional information within the SDK documentation or web. Very helpful during development to keep you code up-to-date with the latest SDK revisions.</li>
|
|
|
48 |
<li><b>Qt SDK for S60 support </b>— Carbide now <a href="qt_help/qt_overview.htm">supports</a> the <a href="qt_help/qt_importing_projs_01.htm">importing</a> and <a href="qt_help/qt_creating_projs_01.htm">creation</a> of Qt projects using the <a href="http://trolltech.com/developer/technical-preview-qt-for-s60">Qt SDK for S60</a>.</li>
|
|
|
49 |
<li><b>Executables view improvements</b> — The <a href="reference/view_executables.htm">Executables</a> view now supports the loading of some additional DLL cases to ensure that the DLLs you want to debug are available during a debug session. In addition, a Remove button has been added to the view's toolbar that makes it easier for you to remove any executables from the list.</li>
|
|
|
50 |
<li><b>More indexer improvements </b>— Speed improvements for code completion, syntax coloring, and much more.</li>
|
|
|
51 |
<li><b>Remote Connections view</b> — A visual list of <a href="reference/trk/view_remote_connection.htm">remote connections</a> and their state for managing multiple and diverse device connections.</li>
|
|
|
52 |
<li><b>Partial upgrade SIS file support</b> — Carbide now supports the generation of partial upgrade SIS/SISX files. This increases debugger turnaround by only generating new files for changes and uploading these smaller execuables to the device.</li>
|
|
|
53 |
<li><b>More Program Counter support </b>— Added a Move to Line command for the debugger that enables you to move the PC to a new line while debugging without executing any intermediate lines or resuming execution.</li>
|
|
|
54 |
<li>Multiple<b> TRK</b> improvements including:
|
|
|
55 |
<ul>
|
|
|
56 |
<li>Both App and System TRK try to disable mobile crash debugging</li>
|
|
|
57 |
<li>TRK now looks for the new mobile crash agent (ms_useragent)</li>
|
|
|
58 |
<li>Added additional error checking when communicating over USB to improve stability</li>
|
|
|
59 |
<li>Fixed some random TRK deadlocks when reading registers or when thread panics occur</li>
|
|
|
60 |
<li>Option > Exit has been replaced by Option > Back to reflect the change made to exiting TRK</li>
|
|
|
61 |
<li>Changes made to use UIDs in place of component names to identify executables for improved identification</li>
|
|
|
62 |
<li>Reset TRK priority to high to avoid problems debugging complex process intensive applications</li>
|
|
|
63 |
<li>Improved breakpoint location in DLLs when debugging multiple processes</li>
|
|
|
64 |
<li>TRK no longer targets processes with UID 0 automatically. Users can still attach to the process or use a launch configuration.</li>
|
|
|
65 |
<li>TRK application name and UID changed to blocking of TRK SIS files assigned with the old UID.</li>
|
|
|
66 |
<li>TRK now always uses the kernel APIs to read/write memory to improve security, no more direct reads/writes.</li>
|
|
|
67 |
<li>Application TRK no longer allows write operations to the following registers: CPSR, SP, and LR</li>
|
|
|
68 |
</ul>
|
|
|
69 |
</li>
|
|
|
70 |
</ul>
|
|
|
71 |
<h4>1.3.1</h4>
|
|
|
72 |
<ul>
|
|
|
73 |
<li><b><a href="reference/trk/wnd_on_device_setup.htm">On-Device Setup</a> </b> dialog — connects, verifies and updates Carbide software services like the TRK debug agent on a device to ensure you are always using the latest version in your development efforts. Having trouble connecting with TRK, give this a try. </li>
|
|
|
74 |
<li><b>New Bug Report wizard </b> — directly submit bugs and enhancement requests to Carbide Bugzilla from within Carbide using the <strong>Help > New Bug Report</strong> menu option. Enter the name and password into the Bug Reporter preference panel and quick bug reports are easy to submit. </li>
|
|
|
75 |
<li><strong>Launch configuration panels UI unification and improvements</strong>— a host of minor UI improvements are being made in the launch configuration panes to provide a more coherent and reproducable experience across all launch configuration dialogs. </li>
|
|
|
76 |
</ul>
|
|
|
77 |
<blockquote>
|
|
|
78 |
<p>For example, the concept of a "main executable" had been replaced with the Executables tab where a list of executables targeted for debugging were shown. This UI change brings the launch configurations into sync with that change by removing the Main Executable from the Main tab. The Main tab will only show a process to launch and not executables targeted for debugging. </p>
|
|
|
79 |
<p>Another example, the Arguments field used by the run-mode TRK configurations has been moved to the Arguments tab to match the Emulator configuration.</p>
|
|
|
80 |
</blockquote>
|
|
|
81 |
<ul>
|
|
|
82 |
<li>Many other bug fixes to improve stability and usability on Carbide </li>
|
|
|
83 |
</ul>
|
|
|
84 |
<h4>1.3.0</h4>
|
|
|
85 |
<ul>
|
|
|
86 |
<li><b>Eclipse 3.3.1.1</b> — The Eclipse 3.3 project provides the foundation, or integration platform, for which the product is built upon. See <a href="PLUGINS_ROOT/org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html">What's New in 3.3</a> for more information.</li>
|
|
|
87 |
<li><b>CDT 4.0.1</b> — This drop is based on a final version of CDT that was part of the Europa release. See the <a href="PLUGINS_ROOT/org.eclipse.cdt.doc.user/concepts/cdt_c_whatsnew.htm">CDT 4.0 News and Noteworthy</a> page for more information. </li>
|
|
|
88 |
<li><b>Build system improvements</b> — large project support has been enhanced for builds and indexing, but performance trade offs have been made so the latter improvements are possible. This is most noticeable when importing projects and making changes to <span class="code">bld.inf</span> and <span class="code">mmp</span> files.</li>
|
|
|
89 |
<li><b>System search</b> — search any directory outside the workspace. </li>
|
|
|
90 |
<li><b>Debugging improvements include:</b>
|
|
|
91 |
<ul>
|
|
|
92 |
<li><b>Executables view</b> — provides a dynamic list of executables and their related source files </li>
|
|
|
93 |
<li><b>Executables tab</b> — uses a rule based approach in launch configurations to include/exclude executables in the project </li>
|
|
|
94 |
<li><b>On-device debugging</b> — lots of TRK (v2.8.6) fixes here to make on-device debugging easier and more stable </li>
|
|
|
95 |
</ul>
|
|
|
96 |
</li>
|
|
|
97 |
<li><b>Carbide tool plug-ins include</b>:
|
|
|
98 |
<ul>
|
|
|
99 |
<li>CodeScanner - a static source code analysis tool for Symbian OS programs written in C++</li>
|
|
|
100 |
<li>Capability Scanner and Epocwind.out Scanner - performs static and runtime capability checks on your project </li>
|
|
|
101 |
<li>Dependency Explorer - analyses static dependencies between components</li>
|
|
|
102 |
</ul>
|
|
|
103 |
</li>
|
|
|
104 |
<li><b>Indexing improvements</b></li>
|
|
|
105 |
<li>The creation of EKA1-based projects has been deprecated with this release. Carbide still supports its use but all development going forward will concentrate on EKA2-based projects. </li>
|
|
|
106 |
<li><b>Lots of bug fixes</b>... </li>
|
|
|
107 |
</ul>
|
|
|
108 |
<h3><a name="beta" id="beta"></a>User Notes</h3>
|
|
|
109 |
<ul><li><b>New extension makefiles</b> - if your project is using the new extension makefile support in OS9.3+ (<span class="code">prj_extensions</span>), you will get a build error with the default builder settings. We plan to fix this issue, but for now you can work around it by disabling the manage dependencies and concurrent compilation builder options found in the <b>Carbide.c++ > Build</b> preference panel.</li>
|
|
|
110 |
<li><b>Qt for Symbian support</b> - The Qt views require registered COM plugins in order to work correctly. These plugins are registered by our installer. If you did not use our installer or have uninstalled an existing Qt Eclipse integration after installing Carbide, you'll need to register the plugins by running a batch file. You'll find the batch file here: \configuration\qt\register_plugins.bat. You'll know that you need to run the batch file if you get exceptions when opening one of the Qt views.</li>
|
|
|
111 |
</ul>
|
|
|
112 |
<h3><a name="issues" id="issues"></a>Fixed bugs and workarounds</h3>
|
|
|
113 |
<ul>
|
|
|
114 |
<li>Complete list of Carbide.c++ <a href="bugs_fixed.htm">bugs fixed</a></li>
|
|
|
115 |
<li>Workarounds for known issues: </li>
|
|
|
116 |
</ul>
|
|
|
117 |
<table cellpadding="0" cellspacing="0" border="0" style="text-align: left; width: 100%;">
|
|
|
118 |
<tbody>
|
|
|
119 |
<tr>
|
|
|
120 |
<th
|
|
|
121 |
style="vertical-align: top; text-align: center; font-weight: bold; ">Summary<br /> </th>
|
|
|
122 |
<th
|
|
|
123 |
style="vertical-align: top; text-align: center; font-weight: bold; ">Workaround</th>
|
|
|
124 |
</tr>
|
|
|
125 |
<tr align="center">
|
|
|
126 |
<td colspan="2" bgcolor="#CBE6C1"><a name="CRITICAL_ITEMS"></a><span class="style8">CRITICAL ITEMS</span></td>
|
|
|
127 |
</tr>
|
|
|
128 |
<tr>
|
|
|
129 |
<td class="style5" style="vertical-align: top;"><b>WARNING:</b> The C/C++ Files view is a view of the actual FILE SYSTEM, so anything deleted in this view is also deleted from the file system. </td>
|
|
|
130 |
<td style="vertical-align: top;"><p>When deleting projects from the workspace please be sure you read the dialog that describes the files that will be deleted. Select the "Do not delete files" option to keep them in the file system.</p> </td>
|
|
|
131 |
</tr>
|
|
|
132 |
<tr>
|
|
|
133 |
<td style="vertical-align: top;"><span class="style5">Carbide.c++ terminates on startup on low memory machines</span></td>
|
|
|
134 |
<td style="vertical-align: top;"> <p>Machines with less than 1GB of memory (or machines runing in a virtual machine) may experience start-up problems. Error dialog typically contains: </p>
|
|
|
135 |
<p><span class="code">JVM terminated, Return code = -1 </span></p>
|
|
|
136 |
<p>or when running from eclipse.exe: </p>
|
|
|
137 |
<p><span class="code">Error occurred during initialization of VM Could not reserve enough space for object heap</span> </p>
|
|
|
138 |
<p>The <a href="hints_tips.htm">solution</a> is to edit your <span class="code">Carbide.c++.1.x.ini</span> (or <span class="code">eclipse.ini</span> if launching Eclipsec.exe) and use a smaller value for the <span class="code">-Xmx </span>paramater to the JVM. </p>
|
|
|
139 |
<p class="note"><b>NOTE</b> In this scenario, Carbide.c++ performance may degrade.</p></td>
|
|
|
140 |
</tr>
|
|
|
141 |
<tr>
|
|
|
142 |
<td style="vertical-align: top;">[4587] Unable to build GCCE targets on Vista because of makefile error.</td>
|
|
|
143 |
<td style="vertical-align: top;">There are known tooling issues when building for the GCCE platform under Windows Vista that can prevent a GCCE build from occurring. If you want to build for GCCE under S60 and UIQ you will need to manually update some files under<span class="style1"> \epoc32\tools\</span>. See the article <a href="http://wiki.forum.nokia.com/index.php/Windows_Vista">Windows Vista</a> for up-to-date workaround information.</td>
|
|
|
144 |
</tr>
|
|
|
145 |
<tr bgcolor="#0071ff">
|
|
|
146 |
<td colspan="2" bgcolor="#CBE6C1" style="vertical-align: top;">
|
|
|
147 |
<div align="center" class="style6"><a name="bug_ide"></a><span class="style8">IDE</span></div> </td>
|
|
|
148 |
</tr>
|
|
|
149 |
<tr>
|
|
|
150 |
<td style="vertical-align: top;">Debugging a project on a machine running Vista via "Remote Desktop Connection" does not work. </td>
|
|
|
151 |
<td style="vertical-align: top;">Workaround: Switch the project to a machine running Windows XP in order to use "Remote Desktop Connection". </td>
|
|
|
152 |
</tr>
|
|
|
153 |
<tr>
|
|
|
154 |
<td style="vertical-align: top;">[6414] Using Mylyn causes MMP files to be spellchecked and common terms like EXE, CPP, and EUSER.LIB flagged as misspellings in editor views </td>
|
|
|
155 |
<td style="vertical-align: top;"><p>Workaround: Remove Mylyn from the Carbide installation. </p> </td>
|
|
|
156 |
</tr>
|
|
|
157 |
<tr>
|
|
|
158 |
<td style="vertical-align: top;">The C/C++ Editor will only work properly with files inside project source folders or on include paths. Source folders are configured in the project settings on the C/C++ Project Paths > Source tab. </td>
|
|
|
159 |
<td style="vertical-align: top;">When creating new folders, use File > New > Source Folder. This will add a folder and mark it a source folder. If you need to import copies of existing files (File > Import > File System) or link to existing sources (File > New > Folder with "Link to folder in file system"), then a normal folder will be created, not a source folder. If the folder is not underneath an existing source folder in the project, you will need to manually mark it as a source folder using the C/C++ Project Paths > Source tab. </td>
|
|
|
160 |
</tr>
|
|
|
161 |
<tr>
|
|
|
162 |
<td style="vertical-align: top;">[3803] Occasionally a module is not expandable immediately after it's been imported in a project. </td>
|
|
|
163 |
<td style="vertical-align: top;">Workaround: Simply close and reopen the project using the context menu in the Project view.</td>
|
|
|
164 |
</tr>
|
|
|
165 |
<tr>
|
|
|
166 |
<td style="vertical-align: top;">[3010] Bad synchronization in MMP editor for Linker definition file.</td>
|
|
|
167 |
<td style="vertical-align: top;"> The templates for Symbian DLL projects do not define a <span class="code">DEFFILE</span> statement, for the case where a <span class="code">DEF</span> file is not needed or imports are not frozen. If you edit the <span class="code">DEF</span> filename through the MMP editor, it is not automatically conditionalized for the current target. If you wish to define target-specific <span class="code">DEF</span> file names in the MMP editor, manually insert <span class="code">#ifdef...#endif</span> blocks, or first uncomment the <span class="code">#ifdef...#endif</span> block from the template, so that target-specific filenames will be properly updated.</td>
|
|
|
168 |
</tr>
|
|
|
169 |
<tr>
|
|
|
170 |
<td style="vertical-align: top;">[2784] Changes to contents of <span class="code">#includes</span> of bld.inf and MMP files are not performed -- instead, changes involving reordering or deleting go to the main file. </td>
|
|
|
171 |
<td style="vertical-align: top;">Workaround: if making changes to nests of included files, either manually edit the <span class="code">#included</span> files, or if using MMP or bld.inf editors, look for changes in the main bld.inf or MMP file and manually fix them up.</td>
|
|
|
172 |
</tr>
|
|
|
173 |
<tr>
|
|
|
174 |
<td style="vertical-align: top;">Indexer coloring for problems</td>
|
|
|
175 |
<td style="vertical-align: top;">The problems marker for the indexer occasionally reports both false negative and false positive results (see indexer bugs below). The problems color by default is set to a dark gray to suggest a possible ambiguous state of the browser. You can change this color under the global preferences page: Syntax Coloring. </td>
|
|
|
176 |
</tr>
|
|
|
177 |
<tr>
|
|
|
178 |
<td style="vertical-align: top;">[4932] Indexer: Problems with templates </td>
|
|
|
179 |
<td style="vertical-align: top;">C++ template navigation is not fully supported yet. Problem areas are notable when templates are declared outside the file they are used and when functions or macros use template declarations. </td>
|
|
|
180 |
</tr>
|
|
|
181 |
<tr>
|
|
|
182 |
<td style="vertical-align: top;">[4937, 4941] Indexer: Problems with macro navigation </td>
|
|
|
183 |
<td style="vertical-align: top;">Browsing to macro declarations is problematic when macros are used within function call parameters as well as multi-line macro declarations.</td>
|
|
|
184 |
</tr>
|
|
|
185 |
<tr>
|
|
|
186 |
<td style="vertical-align: top;">[4931] Indexer does not track files outside the workspace. </td>
|
|
|
187 |
<td style="vertical-align: top;">If you make changes to files outside the workspace the indexer will not re-index these files (e.g. .rsg files under the SDK). When in doubt, re-index your project. </td>
|
|
|
188 |
</tr>
|
|
|
189 |
<tr>
|
|
|
190 |
<td style="vertical-align: top;">[4906] Indexer: const parameters get lost in function prototypes occasionally</td>
|
|
|
191 |
<td style="vertical-align: top;">The indexer sometimes loses the parameter of function types for const objects. In these cases code navigation will not work. </td>
|
|
|
192 |
</tr>
|
|
|
193 |
<tr>
|
|
|
194 |
<td style="vertical-align: top;">Target type macros (__EXE__, __DLL__, etc) are not always defined for the CDT indexer.</td>
|
|
|
195 |
<td style="vertical-align: top;">The CDT indexer macros are build configuration specific. There could be multiple mmp's for a build configuration, each with a different target type macro. Therefore the target type macro is only added if there is only one mmp file, or if all of the mmp's have the same target type macro. You can manually add the macro if you wish using the C/C++ Include Paths and Symbols project property page.</td>
|
|
|
196 |
</tr>
|
|
|
197 |
<tr>
|
|
|
198 |
<td style="vertical-align: top;">The C/C++ Projects and Symbian Project Navigator views do not always refresh with changes in the file system.</td>
|
|
|
199 |
<td style="vertical-align: top;"> If you are in doubt about the contents select the folder in question, then hit F5 to refresh the directory from the file system.</td>
|
|
|
200 |
</tr>
|
|
|
201 |
<tr>
|
|
|
202 |
<td style="vertical-align: top;">Synergy 6.3 Installations will
|
|
|
203 |
always crash Eclipse file navigation dialogs - The solution for this is
|
|
|
204 |
to un-register cmexplorer.dll then reboot your machine. Un-registering
|
|
|
205 |
this feature will only effect users that use Synergy integration to
|
|
|
206 |
Windows Explorer. This issue is known to be fixed with Synergy 6.4.</td>
|
|
|
207 |
<td style="vertical-align: top;">The un-register command is:<br />
|
|
|
208 |
<br />
|
|
|
209 |
<font size="-1"><span class="code"
|
|
|
210 |
style="font-family: courier new,courier,monospace;"> regsvr32 /u
|
|
|
211 |
<path to dll>cmexplorer.dll</span> <br />
|
|
|
212 |
<br />
|
|
|
213 |
</font>To re-register, the command is:<br />
|
|
|
214 |
<br />
|
|
|
215 |
<font size="-1" class="code">regsvr32 <path to
|
|
|
216 |
dll>cmexplorer.dll</font></td>
|
|
|
217 |
</tr>
|
|
|
218 |
<tr bgcolor="#0071ff">
|
|
|
219 |
<td colspan="2" bgcolor="#CBE6C1" style="vertical-align: top;">
|
|
|
220 |
<div align="center" class="style6"><a name="bug_build"></a><span
|
|
|
221 |
class="style8">BUILD/IMPORTER</span></div> </td>
|
|
|
222 |
</tr>
|
|
|
223 |
<tr>
|
|
|
224 |
<td style="vertical-align: top;">[3804] My application fails to start the first time I try to debug it using TRK. </td>
|
|
|
225 |
<td style="vertical-align: top;">Workaround: Launch the debug session again. </td>
|
|
|
226 |
</tr>
|
|
|
227 |
<tr>
|
|
|
228 |
<td style="vertical-align: top;">[3809]<b> IMPORTANT</b>: You cannot import two projects into Carbide that have the same "Root Directory".</td>
|
|
|
229 |
<td style="vertical-align: top;"> If a .project file already exists in this location you either need to shorten or lengthen the "Root Directory" or delete the other project in the same location and try to import again.</td>
|
|
|
230 |
</tr>
|
|
|
231 |
<tr>
|
|
|
232 |
<td style="vertical-align: top;"><p>Emulator (WINSCW) command line builds</p></td>
|
|
|
233 |
<td style="vertical-align: top;"><p>If you want to build for the emulator from the command line, run the tool from the start menu shortcut: <strong>Configure environment for WINSCW command line builds</strong>. It will setup the necessary environment variables for the x86 compiler. You do not need to do this if you will only be building emulator targets from the IDE.</p></td>
|
|
|
234 |
</tr>
|
|
|
235 |
<tr>
|
|
|
236 |
<td style="vertical-align: top;">Working with a workspace on one drive and a source base on another can build some items in the wrong location. </td>
|
|
|
237 |
<td style="vertical-align: top;">Workaround: keep your source base and Carbide workspace on the same drive. Because some scripts work off an implicit root (e.g. \epoc32\include\) and don't support drive specs on paths there can be outputs to unexpected locations. </td>
|
|
|
238 |
</tr>
|
|
|
239 |
<tr>
|
|
|
240 |
<td style="vertical-align: top;">When creating/importing projects the sources and SDK must be on the same drive.</td>
|
|
|
241 |
<td style="vertical-align: top;"> <p>For example, you cannot create a project on the C: drive and build with an SDK whose <span class="code">EPOCROOT</span> is <span class="code">M:\</span>.</p>
|
|
|
242 |
<p> This is due to many of the internal SDK tools using an implicit working drive to calculate paths (e.g. <span class="code">\epoc32\tools</span>).</p></td>
|
|
|
243 |
</tr>
|
|
|
244 |
<tr>
|
|
|
245 |
<td style="vertical-align: top;">Files that include non-ascii
|
|
|
246 |
character types will not compile correctly with GCCE if the file type
|
|
|
247 |
is not saved as UTF-8. </td>
|
|
|
248 |
<td style="vertical-align: top;">The workaround is to change the
|
|
|
249 |
text file encoding in the global preferences at Windows >
|
|
|
250 |
Preferences, then open the General > Editors panel in the
|
|
|
251 |
Preferences window. Look for the Text file encoding option as shown
|
|
|
252 |
below.
|
|
|
253 |
<p align="center"><img src="images/utf.png" width="212" height="68" alt="" /></p> </td>
|
|
|
254 |
</tr>
|
|
|
255 |
<tr>
|
|
|
256 |
<td style="vertical-align: top;">Build system does not detect static library dependencies</td>
|
|
|
257 |
<td style="vertical-align: top;">The Symbian OS build system did not detect static library changes prior to 9.2. They have release a patch for this <a href="http://www3.symbian.com/faq.nsf/0/E0F5C56AA68C305F8025731400051166?OpenDocument">here</a>. </tr>
|
|
|
258 |
<tr bgcolor="#0071ff">
|
|
|
259 |
<td colspan="2" bgcolor="#CBE6C1" style="vertical-align: top;">
|
|
|
260 |
<div align="center" class="style6"><a name="bug_debug"></a><span
|
|
|
261 |
class="style8">DEBUGGER</span></div> </td>
|
|
|
262 |
</tr>
|
|
|
263 |
<tr>
|
|
|
264 |
<td style="vertical-align: top;">Unable to install TRK on flashed devices</td>
|
|
|
265 |
<td style="vertical-align: top;"> Workaround: Some devices contain images that won't allow TRK to be installed, specifically the Lumiere PR 1.0 and PR 1.1 releases, especially if the C drive image was flashed. To install TRK on these devices you must format the C drive to remove the old flash image, then reflash using an image containing TRK.</td>
|
|
|
266 |
</tr>
|
|
|
267 |
<tr>
|
|
|
268 |
<td style="vertical-align: top;">[3778,4658] Some variables show "Invalid format" in the Variable view. </td>
|
|
|
269 |
<td style="vertical-align: top;">No Workaround. </td>
|
|
|
270 |
</tr>
|
|
|
271 |
<tr>
|
|
|
272 |
<td style="vertical-align: top;">Symbian OS Data view caveats. </td>
|
|
|
273 |
<td style="vertical-align: top;"><p>During crash debugger launch session, you can examine Symbian OS data (processes, threads, chunks etc) in Symbian OS Data view. But:</p>
|
|
|
274 |
<p> (1) You must have Symbian kernel debugger (usually <span class="code">Kdebug.dll</span>) built in the image. </p>
|
|
|
275 |
<p> (2) As getting the OS data from crash debugger is time consuming (takes more than one minute in our test), auto-refresh of the data in Symbian OS Data view is disabled for crash debugger. You need to click the "Refresh" button to do a manual refreshing.</p></td>
|
|
|
276 |
</tr>
|
|
|
277 |
<tr>
|
|
|
278 |
<td style="vertical-align: top;">[2616] If you cast a variable to another type the details pane will still show the original type</td>
|
|
|
279 |
<td style="vertical-align: top;">No Workaround. </td>
|
|
|
280 |
</tr>
|
|
|
281 |
<tr>
|
|
|
282 |
<td style="vertical-align: top;">[2960] The thread run control icons (step over, step in, run) are sometimes disabled after stepping</td>
|
|
|
283 |
<td style="vertical-align: top;"> Click on the top frame of the suspended thread in the Debug view</td>
|
|
|
284 |
</tr>
|
|
|
285 |
<tr>
|
|
|
286 |
<td style="vertical-align: top;">Debugging without restarting the emulator.</td>
|
|
|
287 |
<td style="vertical-align: top;"> <p>If you modify any resource files resulting RSC files cannot be rebuilt, however CPP source files can. There are a couple of issues you should be aware of. </p>
|
|
|
288 |
<p>1) When starting a build, the debugger releases all file handles to the debugged application. Sometimes the emulator is slow to release its own handles to files after quitting an application. If a file is still locked on a rebuild make sure the application is closed (not the emulator itself), wait a few seconds, and try again. </p>
|
|
|
289 |
<p> 2) When setting breakpoints in source files that have been recompiled they do not always resolve correctly while the emulator is running. The best option is to clear the breakpoints in any modified file and set them again.</p></td>
|
|
|
290 |
</tr>
|
|
|
291 |
<tr>
|
|
|
292 |
<td style="vertical-align: top;">[2716] [Variable View] - Sometimes when
|
|
|
293 |
stepping through a loop
|
|
|
294 |
variables do not refresh.</td>
|
|
|
295 |
<td style="vertical-align: top;">If you have refresh problems
|
|
|
296 |
with variables, put focus on the variables pane, then off the pane and
|
|
|
297 |
back onto the variable pane.</td>
|
|
|
298 |
</tr>
|
|
|
299 |
<tr>
|
|
|
300 |
<td style="vertical-align: top;">[1928] [Register View] Casting
|
|
|
301 |
Registers to any type does not work.</td>
|
|
|
302 |
<td style="vertical-align: top;">Not currently supported.</td>
|
|
|
303 |
</tr>
|
|
|
304 |
<tr>
|
|
|
305 |
<td style="vertical-align: top;">The value of some uninitialized
|
|
|
306 |
variables is shown as
|
|
|
307 |
"Unknown error ...."</td>
|
|
|
308 |
<td style="vertical-align: top;">When
|
|
|
309 |
variables are in scope the proper value will be displayed.</td>
|
|
|
310 |
</tr>
|
|
|
311 |
<tr>
|
|
|
312 |
<td style="vertical-align: top;">[548] [Variable Scoping] - Multiple
|
|
|
313 |
variables with the same name
|
|
|
314 |
in subscopes are not displayed properly.</td>
|
|
|
315 |
<td style="vertical-align: top;">Give variables unique names.</td>
|
|
|
316 |
</tr>
|
|
|
317 |
<tr>
|
|
|
318 |
<td style="vertical-align: top;">[971] Watchpoints cannot be set on
|
|
|
319 |
global variables declared in header files. </td>
|
|
|
320 |
<td style="vertical-align: top;">No workaround.</td>
|
|
|
321 |
</tr>
|
|
|
322 |
<tr>
|
|
|
323 |
<td style="vertical-align: top;">[1959] Expressions cannot be disabled.</td>
|
|
|
324 |
<td style="vertical-align: top;">No workaround.</td>
|
|
|
325 |
</tr>
|
|
|
326 |
<tr>
|
|
|
327 |
<td style="vertical-align: top;">[Add Global Variables] Not all
|
|
|
328 |
global namespace variables are displayed or duplicate entries sometimes
|
|
|
329 |
appear. </td>
|
|
|
330 |
<td style="vertical-align: top;">No workaround.</td>
|
|
|
331 |
</tr>
|
|
|
332 |
</tbody>
|
|
|
333 |
</table>
|
|
|
334 |
<h3><a name="support" id="support"></a>Technical support </h3>
|
|
|
335 |
<p>The following support services are available:</p>
|
|
|
336 |
<ul><li>Visit the <a href="http://discussion.forum.nokia.com/forum/forumdisplay.php?s=&forumid=95">Forum Nokia Developer Discussion Board</a> for lively Carbide.c++ discussions </li>
|
|
|
337 |
<li>Forum Nokia Wiki - visit <a href="http://wiki.forum.nokia.com/index.php/Carbide.c++">wiki.forum.nokia.com/index.php/Carbide.c++</a> for updated information, downloads and tips </li>
|
|
|
338 |
<li>Customer feedback - send your comments and suggestions to <a href="mailto:feedback.carbide@nokia.com">feedback.carbide@nokia.com</a></li>
|
|
|
339 |
<li>Read the <a href="http://sw.nokia.com/id/d11442a8-4eb1-4c01-97f2-fd8be139b93f/Carbide_cpp_On_Device_Debugging_v1_0_en.pdf">Carbide.c++ On-device Debugging</a> whitepaper or an introduction to on-device debugging for S60 3rd Edition devices<br />
|
|
|
340 |
</li>
|
|
|
341 |
</ul>
|
|
|
342 |
<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
|
|
|
343 |
|
|
|
344 |
</body>
|
|
|
345 |
</html> |