Register with Forum Nokia now and you'll enjoy the full benefits of the Forum Nokia membership.
Register LoginS60 C++ Code_Snippet Flash_Lite Go-to-Market N95 N-Series performance usability
A tour to the S60 Touch UI components
Luis Valente
Read more about Luis Valente on the Champions web site.
Sign up for our free, biweekly newsletter to keep up with the latest information.
Series 40 6th Edition SDK is now available!
Forum Nokia is Calling All Innovators! Enter the contest and you could win $35,000.
Mobile Software Forum
December 16, 2008
St. Petersburg, Russia
2009 International CES
January 08, 2009
Las Vegas
Java™ Mobile, Media & Embedded Developer Days Conference
January 21, 2009
Santa Clara, California
GSMA Mobile World Congress
February 16, 2009
Barcelona, Spain
NFC Congress 2009
February 24, 2009
Hagenberg, Austria
Carbide.c++ Professional Edition extends the features of Developer Edition by providing the tools required by developers creating mission-critical applications that ship with devices or that need to make optimal use of a device’s CPU, memory, and power resources.
The Carbide.c++ Performance Investigator is a sampling profiler. It provides developers with tools that allow them to investigate an application’s relative CPU load, memory usage, and power consumption on a device. Power consumption information is available only from devices with power management hardware.
CPU load analysis can be performed on individual threads. The Performance Investigator Analyzer then allows developers to drill down to binaries and function callers and callees, to isolate the source of the load. Thread and binary load information can be acquired without target device sources, but for best results, access to the device’s ROM image-symbol file is required. Information in the Performance Investigator Analyzer can now be copied to the clipboard and pasted into a spreadsheet application such as Microsoft Excel or saved to a comma-separated values (*.csv) file.
Carbide.c++ Professional Edition delivers system-level on-device debugging with System TRK. Attaching to system threads, unrestricted views into system memory, and the ability to debug applications loaded from RAM/ROFS and ROM ensure that coding problems can be found regardless of the source.
System-level on-device debugging adds visibility to system-level code and memory to the debugging environment. This is especially important for developers working on new-device designs or developers testing their applications with preproduction prototypes. It requires devices on which the manufacturer has installed an R&D certificate.
The CodeScanner static analysis tool scans code to detect potential problems such as incomplete memory cleanup and excessive code. CodeScanner can help developers improve the quality of their code and reduce the time spent debugging by enabling the detection of problem code early in the development cycle.
The Dependency Explorer enables developers to analyse the static dependencies between components in a Symbian C++ application. The tool is useful for troubleshooting complex code relationships and, as such, is an aid to writing more efficient code.
The new GUI crash debugger allows developers to connect to a crashed device with a running crash debugger. In Carbide.c++, details of the source code, variables, and registers for the thread that caused the crash can be viewed.
Support is provided for on-device debugging and performance investigation on prototype and R&D devices.
This capability must be enabled by a device manufacturer.
Support is provided for developers to use custom (nonpublic) SDKs (CustKits). In addition, the devices.xml file of the SDK properties can be edited directly from within Carbide.c++.
For information on the features of the other editions of Carbide.c++, please see the following pages: Carbide.c++ Developer Edition features and Carbide.c++ OEM Edition features. Alternatively, download and read the Carbide.c++ data sheet.