Debugging Comms

This topic provides a summary of help available to debug the components of Cellular Baseband Services, Communication Framework and Networking Services modules.

Note: Before you start to debug, check the Comms software configuration since some configuration options may help with the task. For more information see Software Behaviour in a Debug Environment. Also, some software problems are caused by an incorrect configuration. For more information on the configuration options in Comms, see Comms Configuration.

Textual logging by the Symbian platform Comms software is the primary means by which Comms software can be debugged. By default, this textual logging is built into the debug Comms binary files and not into release binary files. Mobile phone software contains the release versions of the binary files. To debug the code you must use substituted debug binary files. These debug binary files may also contain behavioural changes to make errors more apparent and error tracing easier. These behaviour changes can also mask software problems that are influenced by differences in timing. For more information see Textual Logging and How to Use ULogger with Comms.

For more information on debugging using On-target hardware see On-target Debugging.

For more information on debugging specific Comms components see Component-Specific Debugging Help.

For information on the lower-level aspects of debugging such as the memory map, process priorities and thread states see Debugging information.

The Hooklogger application can be useful in tracking software defects such as memory leaks, stray signals and non-trapped leaves. For more information on Hooklogger in general see Detecting Comms memory leaks.