Namespaces

Variants
Actions

Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

Getting Started with On-Device Debugging using Carbide.c++

From Wiki
Jump to: navigation, search
Article Metadata
Dependencies: Carbide.c++ 2.0
Article
Created: rebloor (13 Mar 2007)
Last edited: hamishwillee (17 Jul 2012)

Needs-update.pngThis article needs to be updated: If you found this article useful, please fix the problems below then delete the {{ArticleNeedsUpdate}} template from the article to remove this warning.

Reasons: hamishwillee (20 Oct 2011)
Carbide.c++ debugging has significantly improved from v3. This article points to out of date references and broken links. It also refers to old professional/OEM/express branding. Merge with Carbide.c++ On-device Debugging Quick Start

Note: For the latest information on using the debugging features in Carbide.c++ please see the "Debugging projects" section of the Carbide.c++ help.

For those of you who have not yet checked out the features for On-Device Debugging (ODD) in Carbide.c++ Developer, Professional, and OEM see videos or read the help files that come with Carbide.

Both resources guide you through the basics of setting up the ODD software, building the application, and running an on-device debug session. The white paper also includes a handy troubleshooting guide.

TRK Files

With the release of Carbide.c++ v2.0, downloading the latest TRK and Performance Investigator (PI) agents is accomplished using the Install Remote Agents pane in the "New Connection Wizard".


This page was last modified on 17 July 2012, at 05:22.
82 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×