I doubt any of you will ever need to submit bug reports since Carbide.c++ is perfect in every way (ahem), but the Bug Reporting dialog can help you generate defect or enhancement reports more quickly and completely…

In run-mode the Carbide.c++ v2.0 debugger now supports the auto-targeting of processes that are already running or created during the execution of a debug session. Previously, the debugger forced users to explicitly attach to a running process. Now, the debugger attempts to target all the EXEs specified in the Executables tab of the launch configuration.

If the executables are already started, it gets the load address of the executable and targets it for debugging, resolving any breakpoints it finds.
The [...]

Many moons ago I mentioned in Online Carbide Documentation Push that I wanted to publish our Carbide docs to the web for all to see and use. The main reason for this push was to make all Carbide info available via Google searches. The second reason I’m happy to have the material online is so that anyone can now link to the info using standard URLs. No more long title paths like Carbide.c++ User Guide > Creating programs [...]

Coming soon to a desktop near you will be the latest version of Carbide.c++, namely version 2.0. Most of you know already that Carbide is made from a diverse set of plugins that operate on the Eclipse framework. Many of the improvements we provide come not from us but from the Eclipse community that spent countless hours adding new features to the Eclipse Ganymede release, version 3.4. Using that release as a base we added in the CDT 5.0 plug-ins [...]

So, I’m up in Dallas passing on information to one of the many internal Nokia groups on the current features in Carbide as well as some upcoming technologies we plan to support RSN. With all the new features to be shipped with Carbibe 2.0 it’s sometimes hard to remember that others have not already spent 3+ years working with it nor know all of its little secrets. OK, to be honest I don’t know them all either, but with all [...]

A new feature for Carbide v2.0 is the remote connections UI framework. The framework allows Carbide users to create remote connections data objects that are stored in the workspace, can be exported and imported, and can be shared among multiple instances of use (for now, on-device launch configurations).
Some of the benefits are that once a remote connection object is created and its data is specified, it can be named and reused without having to specify the data again. Also, if [...]

Debugging multiple processes at once in Carbide can be a little tricky but this is an area where we’re making some improvements for 2.0. When you are using the emulator then Carbide is really debugging epoc.exe and not the individual Symbian OS processes. So if you terminate debugging one of the processes you’ll take down the entire emulator. But when debugging on a real phone then you can terminate each process individually.

You can also right-click on a process in the [...]

One thing that can confuse some users that are new to Eclipse and Carbide.c++ is the concept of the workspace and how Carbide.c++ makes use of it. Adding to this confusion can be the root directory concept along with some of its limitations, so I figured I would create a screencast for this. So without further delay, take a look at this introduction to these concepts:

You can find this and other videos at: http://wiki.forum.nokia.com/index.php/Carbide_Training_Videos

Got ideas for [...]

I’ve been working with Ravi to plug a hole in our debugger use cases for Carbide 2.0: usually if you start a debug session in Carbide it will determine what executables you are interested in and let you set breakpoints there. But what if you decide you want to debug additional DLLs after a debug session has started? You can’t do this in Carbide 1.3 without terminating the debug session and starting over again. In Carbide 2.0 you can now [...]

My work this week on Carbide 2.0 was focused on cleaning up problems dealing with executable files. Several people had reported cases where their executables remained locked after a debug session. I was able to reproduce at least one of them and put a fix into the next nightly build.

I also cleaned up an assortment of minor issues with the Executables View and added a “Remove” button to let you easily remove executable files you import for debugging. You [...]