## Debugging in ROM

You will see symbolic information for other components when you are debugging in ROM using System TRK if those components were built with symbolic information and the ROM Log file is specified. If a function in the stack crawl is in a ROM module and the IDE is able to find a file containing symbolic information for that module, the IDE will load it automatically and display function names. The IDE will also allow source level debugging and let you set breakpoints in this module.

Some issues to pay attention to when debugging include:

- In System TRK you must specify the ROM log file in the ROM Log tab of the TRK or Attach to Process launch configurations

> NOTE You cannot debug ROM DLLs using Application TRK.

- In Trace32 you must specify the ROM log file in the ROM Image tab of the Trace32 launch configuration

##### Other references

- Importing Executables for Debugging
- Symbian OS Trace32 Support