Carbide.c++ Release Notes 3.0.0

Once you have read the release notes, we recommend you follow the

HelloWorld tutorial for @@ -34,11 +29,21 @@

WARNING: Updating the CDT feature in Carbide.c++/Eclipse will wipe out our changes making the tools unusable!

See the Tips & tricks page for more helpful information.

What's New in 3.0.0

The following features for Symbian development are provided within Carbide.c++:

Nada supported — ???

Eclipse 3.6 — The Eclipse 3.6 project (Helios) provides the foundation, or integration platform, on which Carbide.c++ is built. See What's New in 3.6 for more information.

CDT 7.0 — The final version of CDT is included as part of the Helios release. See the CDT 7.0 News and Noteworthy page for more information.

Eclipse Debugger for C/C++ — Carbide now uses the Eclipse Debugger for C/C++ (EDC) as its default debugger. EDC provided an entirely new Debug view with all of the standard debug features like variables, breakpoints, watchpoints, disassembly, and all the other views required to run a debugging session. In addition, EDC provides the framework to add new debug features like snapshots.

Customized Carbide environment — Carbide introduces Plugin Discovery Sites where you can search for and download Carbide plugins to customize your Carbide environment. Think of it as an app store for plugins. It uses the Eclipse P2 feature to provide a common framework for finding, installing, updating, and removing plugins from the Carbide environment.

Improved UI — Carbide's UI has been streamlined and minimized to a core set of functionality, mainly that of creating Symbian projects, building and debugging them. Context menus have been reworked to show a minimum set of options. If your favorite option is missing, you can use the Capability preference panel or the Customize Perspective dialog to add favorite commands back onto the context menus.

Performance improvements — We continue to address known performance issues as they reveal themselves. This release provides improvements for: +

Stack frames — in the Debug view stack frames were displayed once the symbol tables were completely read. For large symbol files this sometimes slowed down the display and hence the ability to continue debugging. Now the Debug view will show a subset of stack frames after a set time and update the remainder once it has finished scanning the symbol file.
Executables view — eliminated several use cases that forced the Executables list to update to frequently.
Large symbol tables supported — The Carbide symbol reader has been rewritten to provide faster access to symbols and to handle very large symbol files (larger than 10GB).

2.6.0

@@ -66,233 +71,11 @@

RVCT 4.0 (ARMv5) builds and some limited debugging is supported

Symbian ^3 SDK now supported

Fixed bugs and workarounds

Known issues

Workarounds for known issues:

Complete list of Carbide.c++ bugs fixed

Workarounds for known issues:

Qt issues — If Qt does not seem to be working as expected, be sure to run the \configuration\qt\register_plugins.bat file to properly register the Qt plugins. This is especially important if you installed Carbide using a zip file and not an installer.

Summary	Workaround
KNOWN PnP ISSUES in 2.5
Connecting multiple devices	If multiple devices are plugged into USB, Carbide sometimes cannot determine the USB personality of either or both devices. Carbide will log an error that says the "getting/setting of USB personality" was not supported and no connection is created. The work-around is to plug only one device in.
Multiple same error warnings	- If a single device is plugged in, and Carbide logs the same error, this is an indication that either - A. the PCSuite/OVISuite drivers are not up-to-date or - B. the device does not support switching to PC/OVI Suite mode from its current mode - For case A, try installing a later version of PCSuite. For case B, set the default USB mode to PC/OVI Suite mode in the settings on the device or selecting PC/OVI Suite mode when the device asks which USB mode to select. -
PC Suite fails to send updates	On some devices, when unplugging and plugging back in the same USB mode, PC Suite will fail to notify that the device disconnected and the personality switch bubble will not pop up. As a work-around, change the default mode and plug in the device again.
CRITICAL ITEMS
WARNING: 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.	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.
Carbide.c++ terminates on startup on low memory machines	Machines with less than 1GB of memory (or machines running in a virtual machine) may experience start-up problems. Error dialog typically contains: - JVM terminated, Return code = -1 - or when running from eclipse.exe: - Error occurred during initialization of VM Could not reserve enough space for object heap - The solution is to edit your Carbide.c++.2.x.ini (or eclipse.ini if launching Eclipsec.exe) and use a smaller value for the -Xmx parameter to the JVM. - NOTE In this scenario, Carbide.c++ performance may degrade.
[4587] Unable to build GCCE targets on Vista because of makefile error.	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 \epoc32\tools\. See the article Windows Vista for up-to-date workaround information. - UPDATE 2010: SDKs still require patching to enable GCCE builds.
- IDE
Debugging a project on a machine running Vista via "Remote Desktop Connection" does not work.	Workaround: Switch the project to a machine running Windows XP in order to use "Remote Desktop Connection".
[6414] Using Mylyn causes MMP files to be spell checked and common terms like EXE, CPP, and EUSER.LIB flagged as misspellings in editor views	Workaround: Remove Mylyn from the Carbide installation.
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.	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.
[3010] Bad synchronization in MMP editor for Linker definition file.	The templates for Symbian DLL projects do not define a DEFFILE statement, for the case where a DEF file is not needed or imports are not frozen. If you edit the DEF filename through the MMP editor, it is not automatically conditioned for the current target. If you wish to define target-specific DEF file names in the MMP editor, manually insert #ifdef...#endif blocks, or first uncomment the #ifdef...#endif block from the template, so that target-specific filenames will be properly updated.
[2784] Changes to contents of #includes of bld.inf and MMP files are not performed -- instead, changes involving reordering or deleting go to the main file.	Workaround: if making changes to nests of included files, either manually edit the #included 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.
Indexer coloring for problems	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.
[4932] Indexer: Problems with templates	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.
[4937, 4941] Indexer: Problems with macro navigation	Browsing to macro declarations is problematic when macros are used within function call parameters as well as multi-line macro declarations.
[4931] Indexer does not track files outside the workspace.	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.
[4906] Indexer: const parameters get lost in function prototypes occasionally	The indexer sometimes loses the parameter of function types for const objects. In these cases code navigation will not work.
Target type macros (__EXE__, __DLL__, etc) are not always defined for the CDT indexer.	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.
The C/C++ Projects and Symbian Project Navigator views do not always refresh with changes in the file system.	If you are in doubt about the contents select the folder in question, then hit F5 to refresh the directory from the file system.
Synergy 6.3 Installations will always crash Eclipse file navigation dialogs - The solution for this is to un-register cmexplorer.dll then reboot your machine. Un-registering this feature will only effect users that use Synergy integration to Windows Explorer. This issue is known to be fixed with Synergy 6.4.	The un-register command is: - - regsvr32 /u -<path to dll>cmexplorer.dll - - To re-register, the command is: - - regsvr32 <path to -dll>cmexplorer.dll
- BUILD/IMPORTER
[3809] IMPORTANT: You cannot import two projects into Carbide that have the same "Root Directory".	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.
Emulator (WINSCW) command line builds	If you want to build for the emulator from the command line, run the tool from the start menu shortcut: Configure environment for WINSCW command line builds. 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.
Working with a workspace on one drive and a source base on another can build some items in the wrong location.	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.
When creating/importing projects the sources and SDK must be on the same drive.	For example, you cannot create a project on the C: drive and build with an SDK whose EPOCROOT is M:\. - This is due to many of the internal SDK tools using an implicit working drive to calculate paths (e.g. \epoc32\tools).
Files that include non-ascii -character types will not compile correctly with GCCE if the file type -is not saved as UTF-8.	The workaround is to change the -text file encoding in the global preferences at Windows > -Preferences, then open the General > Editors panel in the -Preferences window. Look for the Text file encoding option as shown -below. -
Build system does not detect static library dependencies	The Symbian OS build system did not detect static library changes prior to 9.2. They have release a patch for this here.
- DEBUGGER
Unable to install TRK on flashed devices	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.
[3778,4658] Some variables show "Invalid format" in the Variable view.	No Workaround.
Symbian OS Data view caveats.	During crash debugger launch session, you can examine Symbian OS data (processes, threads, chunks etc) in Symbian OS Data view. But: - (1) You must have Symbian kernel debugger (usually Kdebug.dll) built in the image. - (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.
[2960] The thread run control icons (step over, step in, run) are sometimes disabled after stepping	Click on the top frame of the suspended thread in the Debug view
Debugging without restarting the emulator.	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. - 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. - 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.
[2716] [Variable View] - Sometimes when -stepping through a loop -variables do not refresh.	If you have refresh problems -with variables, put focus on the variables pane, then off the pane and -back onto the variable pane.
[1928] [Register View] Casting -Registers to any type does not work.	Not currently supported.
The value of some uninitialized -variables is shown as -"Unknown error ...."	When -variables are in scope the proper value will be displayed.
[548] [Variable Scoping] - Multiple -variables with the same name -in subscopes are not displayed properly.	Give variables unique names.
[971] Watchpoints cannot be set on -global variables declared in header files.	No workaround.
[1959] Expressions cannot be disabled.	No workaround.
[Add Global Variables] Not all -global namespace variables are displayed or duplicate entries sometimes -appear.	No workaround.

Summary

Workaround

KNOWN PnP ISSUES in 2.5

Connecting multiple devices

If multiple devices are plugged into USB, Carbide sometimes cannot determine the USB personality of either or both devices. Carbide will log an error that says the "getting/setting of USB personality" was not supported and no connection is created. The work-around is to plug only one device in.

Multiple same error warnings

If a single device is plugged in, and Carbide logs the same error, this is an indication that either

A. the PCSuite/OVISuite drivers are not up-to-date or

B. the device does not support switching to PC/OVI Suite mode from its current mode

For case A, try installing a later version of PCSuite. For case B, set the default USB mode to PC/OVI Suite mode in the settings on the device or selecting PC/OVI Suite mode when the device asks which USB mode to select.

PC Suite fails to send updates

On some devices, when unplugging and plugging back in the same USB mode, PC Suite will fail to notify that the device disconnected and the personality switch bubble will not pop up. As a work-around, change the default mode and plug in the device again.

CRITICAL ITEMS

WARNING: 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.

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.

Carbide.c++ terminates on startup on low memory machines

Machines with less than 1GB of memory (or machines running in a virtual machine) may experience start-up problems. Error dialog typically contains:

JVM terminated, Return code = -1

or when running from eclipse.exe:

Error occurred during initialization of VM Could not reserve enough space for object heap

The solution is to edit your Carbide.c++.2.x.ini (or eclipse.ini if launching Eclipsec.exe) and use a smaller value for the -Xmx parameter to the JVM.

NOTE In this scenario, Carbide.c++ performance may degrade.

[4587] Unable to build GCCE targets on Vista because of makefile error.

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 \epoc32\tools\. See the article Windows Vista for up-to-date workaround information.

UPDATE 2010: SDKs still require patching to enable GCCE builds.

IDE

Debugging a project on a machine running Vista via "Remote Desktop Connection" does not work.

Workaround: Switch the project to a machine running Windows XP in order to use "Remote Desktop Connection".

[6414] Using Mylyn causes MMP files to be spell checked and common terms like EXE, CPP, and EUSER.LIB flagged as misspellings in editor views

Workaround: Remove Mylyn from the Carbide installation.

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.

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.

[3010] Bad synchronization in MMP editor for Linker definition file.

The templates for Symbian DLL projects do not define a DEFFILE statement, for the case where a DEF file is not needed or imports are not frozen. If you edit the DEF filename through the MMP editor, it is not automatically conditioned for the current target. If you wish to define target-specific DEF file names in the MMP editor, manually insert #ifdef...#endif blocks, or first uncomment the #ifdef...#endif block from the template, so that target-specific filenames will be properly updated.

[2784] Changes to contents of #includes of bld.inf and MMP files are not performed -- instead, changes involving reordering or deleting go to the main file.

Workaround: if making changes to nests of included files, either manually edit the #included 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.

Indexer coloring for problems

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.

[4932] Indexer: Problems with templates

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.

[4937, 4941] Indexer: Problems with macro navigation

Browsing to macro declarations is problematic when macros are used within function call parameters as well as multi-line macro declarations.

[4931] Indexer does not track files outside the workspace.

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.

[4906] Indexer: const parameters get lost in function prototypes occasionally

The indexer sometimes loses the parameter of function types for const objects. In these cases code navigation will not work.

Target type macros (__EXE__, __DLL__, etc) are not always defined for the CDT indexer.

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.

The C/C++ Projects and Symbian Project Navigator views do not always refresh with changes in the file system.

If you are in doubt about the contents select the folder in question, then hit F5 to refresh the directory from the file system.

Synergy 6.3 Installations will always crash Eclipse file navigation dialogs - The solution for this is to un-register cmexplorer.dll then reboot your machine. Un-registering this feature will only effect users that use Synergy integration to Windows Explorer. This issue is known to be fixed with Synergy 6.4.

The un-register command is:
-
- regsvr32 /u -<path to dll>cmexplorer.dll
-
- To re-register, the command is:
-
- regsvr32 <path to -dll>cmexplorer.dll

BUILD/IMPORTER

[3809] IMPORTANT: You cannot import two projects into Carbide that have the same "Root Directory".

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.

Emulator (WINSCW) command line builds

If you want to build for the emulator from the command line, run the tool from the start menu shortcut: Configure environment for WINSCW command line builds. 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.

Working with a workspace on one drive and a source base on another can build some items in the wrong location.

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.

When creating/importing projects the sources and SDK must be on the same drive.

For example, you cannot create a project on the C: drive and build with an SDK whose EPOCROOT is M:\.

This is due to many of the internal SDK tools using an implicit working drive to calculate paths (e.g. \epoc32\tools).

Files that include non-ascii -character types will not compile correctly with GCCE if the file type -is not saved as UTF-8.

The workaround is to change the -text file encoding in the global preferences at Windows > -Preferences, then open the General > Editors panel in the -Preferences window. Look for the Text file encoding option as shown -below. -

Build system does not detect static library dependencies

The Symbian OS build system did not detect static library changes prior to 9.2. They have release a patch for this here.

DEBUGGER

Unable to install TRK on flashed devices

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.

[3778,4658] Some variables show "Invalid format" in the Variable view.

No Workaround.

Symbian OS Data view caveats.

During crash debugger launch session, you can examine Symbian OS data (processes, threads, chunks etc) in Symbian OS Data view. But:

(1) You must have Symbian kernel debugger (usually Kdebug.dll) built in the image.

(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.

[2960] The thread run control icons (step over, step in, run) are sometimes disabled after stepping

Click on the top frame of the suspended thread in the Debug view

Debugging without restarting the emulator.

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.

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.

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.

[2716] [Variable View] - Sometimes when -stepping through a loop -variables do not refresh.

If you have refresh problems -with variables, put focus on the variables pane, then off the pane and -back onto the variable pane.

[1928] [Register View] Casting -Registers to any type does not work.

Not currently supported.

The value of some uninitialized -variables is shown as -"Unknown error ...."

When -variables are in scope the proper value will be displayed.

[548] [Variable Scoping] - Multiple -variables with the same name -in subscopes are not displayed properly.

Give variables unique names.

[971] Watchpoints cannot be set on -global variables declared in header files.

No workaround.

[1959] Expressions cannot be disabled.

No workaround.

[Add Global Variables] Not all -global namespace variables are displayed or duplicate entries sometimes -appear.

No workaround.

Technical support

The following support services are available:

Visit the Symbian Foundation for Carbide.c++ and Symbian development information