Debugging and logging information is very necessary while developing in RDK. This helps to debug/track the applications running in RDK stack. 

Debugging

are both inseparable aspects of any software system during it's development as well as in the deployment stage. These tools greatly assist the developer & support teams to quickly find a solution.

• Debugging tools and methodologies identifies what's went wrong thus enabling developer to fix the issue quickly.
• Logging enables to maintain a history of how a software or the piece of code behave in different environments (whether it is in development or in field deployment). It helps in catching nagging field issues which are otherwise impossible to reproduce in a simulated environment. Also the other advantage it provides by generating a solid data set for any analytics process.

Debugging

In the development process of a feature rich software like RDK, debugging the code or modules bears great significance. While integrate development environments (IDE) provide a great deal by helping to solve certain debug functionalities, when working with a Set-top it is also important to have debuggers that can collect core dumps and real time code traces.

RDK supports following tools for making the debugging task easier for developers. There are several tools that can aid in debugging in RDK stack. Important ones are:

• rmfApp
• Breakpad
  
  

Logging