|
» Subscribe » Favorite Links » What is S60? » Freeware & Trials » S60 devices » Hints and tips » About this blog |
» Blognotes (15) » Bugs and Workarounds (4) » Build tools (5) » Carbide.c++ 1.1 (4) » Carbide.c++ 1.2 (8) » Carbide.c++ 1.3.x (9) » Carbide.c++ 2.0.x (12) » Carbide Plug-Ins (4) » CodeWarrior (2) » FAQ (6) » Future directions (25) » General (48) » Off-topic (5) » On-device debugging (13) » Performance Investigator (2) » Product features (18) » Product releases (16) » Screencast (14) » Support (36) » Tool setup (6) » UI Designer (8) » Usability (18) » Work in Progress (14) » Write-build-debug (4) |
|
» What's your excuse? » Carbide.c++ wins Jolt Award! » SCREENCAST: Performance Investigator » Screencast: On-device debugging with Carbide.c++ 1.1 |
|
Subscribe to RSS feed For email notification, please click here ยป |
There has been a flurry of recent support questions on creating projects, debugging, and a host of other minor issues that doesn't include enough information to actually solve the problem. Upon further investigation it's discovered that the person is still using Carbide 1.2 or GASP, 1.1 as their development environment.
So the question is, why haven't you upgraded to Carbide 1.3 yet?
Carbide 1.3 includes support for Eclipse 3.3 and CDT 4.0, a host of build system improvements for large projects and indexing, a new System search capability, new debugger improvements like the Executables view and improved on-device debugger stability, new tool plug-ins like CodeScanner, Capability Scanner, Epocwind.out, and lots of bug fixes.
Carbide 1.1 and even parts of 1.2 really pale in comparison to what Carbide 1.3 offers. If this small message has struck a chord somewhere, go download the latest version here. Especially you Carbide 1.1 users as I'm sure you'll be pleasantly surprised at the improvements.
The real answer?
There is no excuse!
I woke this morning to get an SMS from our marketing manager (and future Carbide.c++ product manager) Mike Trujillo saying that Carbide.c++ Professional Edition had won the Jolt Award 2007 for Best Mobile Development Tool. Yiihaa!
So what's a Jolt award anyway? it's an award handed out by Dr. Dobb's magazine every year, and the website says it's the Oscars of software tools :-)
Needless to say, we're feeling pretty good over here. The team is currently fixing bugs like mad in order to get the final release candidate built next week, and I'd venture to say this will make the final crunch all the more enjoyable.
Please join me in congratulating the engineering team for their achievement!
Wow, it's been a while... A happy new year to all!
I wanted to take some of your time to show off some of the features in Carbide.c++ 1.1 Professional Edition. Performance Investigator allows you to track the CPU consumption of individual threads and functions, and to identify which binaries those threads/functions are associated with. Additionally, you can analyze the caller/callee relationships of a given function.
The basic concept is that you install the PI agent on the target device, start PI sampling, start your app, run your favorite performance-hogging use case, and then stop the PI agent. PI will save the file on the device. Once you've moved the file over to the PC, you need to pair it with the project you're analyzing to view thread loads of your app only. Or, if you work in device creation and have access to ROM files, you can pair it with symbol files to get a complete view of the system.
The software works on-device with S60 3rd Edition phones, including final releases and CE devices. Versions are also available for UIQ/SEMC phones, although the agent is currently not available publicly -- only to those working on SEMC device creation projects.
Download the screencast here. (Apologies, it's an EXE file)
After some initial troubles, a screencast about how to do on-device debugging with Carbide.c++ is available on Forum Nokia. As always, let me know what you think, and what is missing.