## ROM Log page

Use the ROM Log page to specify where the ROM log file is stored and the Epoc32 directory.

Figure 1. ROM Log page

##### Table 1. ROM Log page—items

Item | Explanation
--- | ---
Parse Rom Log File | Activate the Parse ROM Log File option and specify the information that the debugger needs in order to show detailed stack information, set breakpoints, and show source level debugging information for ROM images.
Symbian Rom Log File | In the Symbian Rom Log File text field, browse to or enter the full path and name of the log file that corresponds to the ROM image on the target device. This log file is generated by default when the ROM image is built.
Symbian Epoc32 Directory | Specifies the epoc32 directory in which the ROM image and log files are stored. Since the log file may not contain full paths to the ROM components on the host PC, you need to enter this epoc32 directory. NOTE Always include the epoc32 folder in this path.
Log unresolved modules | Activate the Log unresolved modules option to have the debugger output a list of components from the specified ROMBUILD log file that do not have debugger symbolic information. The list is displayed in the debugger console window at the beginning of the debug session. NOTE You cannot perform source-level debugging on components that do not include symbolic information.

##### Related tasks

- Stop Mode On-Device Debugging Preconditions