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. Thanks for all your past and future contributions.

Debugging Symbian C++ application with CODA for Symbian OS

From Wiki
Jump to: navigation, search
Article Metadata
Code Example
Installation file: File:Coda
Created: mahbub_s60 (29 Dec 2011)
Last edited: pavan.pareta (06 Jun 2013)

Debugging Symbian C++ application with CODA for Symbian OS



Debugging is one of the most important phase of software development. Specially for software development with embedded system where development environment is not in host device. There are some debugging articles that describes well with other software tool and for other platform. For example in the following article, there is good description of debugging with 5th edition device software with TRK ( In this article we are going to describe how we can use CODA on device debugging agent with Carbide tool for Symbian platform. In this article, Belle SDK has been used to demonstrate all the steps to debug helloCoda application.

What Software We need

We need the followings software/hardware.
-CODA on device debugging tool File:Coda
-Belle SDK
-A device for example Nokia 700 for example with USB cable

Steps for debugging

1. Create new project or import the existing project to Carbide environment

2. Select Run | Debug Configurations | Edit | Install Remote Agents (If we don’t have installed CODA in our device).The tool can be saved to PC and installed or can be installed directly if the device is connected to our PC (we need ovi suite to be installed in our PC)

Codadebug 01.png 

3. Run the CODA in device and select Connect. The CODA application should show status as Connected as shown in the following image.
Codadebug 02.png

4. Configure carbide with your certificate Project | Properties | Carbide C++ | Build Configuration | SIS Builder | Add Codadebug 03.png

5. Compile and link your application with Carbide IDE and make sure there is no error.

6. Run | Debug As (we need to check debug configuration if we have not done it already)

Codadebug 04.png

If we put any break point in our code at that point execution should stop and we can use Step Over, Step into etc. at this point to check some statements how these are executing and also check variables where we are interested in.

Another alternative way to check variables and statement are using RDebug::Print(….). This will print any variables or debug string those are inserted in code. Handy way to use this is include the debug.h in our project inc folder and included debug library in our mmp files. We need to include debug.h file in our cpp file where we are interested in. For example we want to check the value of aCommand in void CHelloCodaAppUi::HandleCommandL(TInt aCommand) We can include the following line to see the result in console output, for example in the following line we can see the value of aCommand in the Console output window. TRACE_INFO ((_L("void CHelloCodaAppUi::HandleCommandL aCommand = %d"), aCommand));

Sample applications

Following zip file include the debug.h file that can be readily use for debugging purposes.

This page was last modified on 6 June 2013, at 02:51.
89 page views in the last 30 days.