CrossWorks for ARM User Guide

15DialogsDebug file search editorWhen a program is built with debugging enabled the debugging informationcontains paths describing where the source files that went into the program arelocated in order to allow the debugger to find them. If a program or libraries linkedinto the program are being run on a different machine to the one they were compiledon or if the source files have moved since the program was compiled, the debuggerwill unable to find the source files.In this situation the simplest way to help CrossStudio find the moved source files isto add the directory containing the source file to one of its source file search paths.Alternatively, if CrossStudio cannot find a source file it will prompt you for itslocation and record it's new location in its source file map.Debug source file search pathsThe debug source file search paths can be used to help the debugger locate source filesthat are no longer in the same location as they were at compile time. When a sourcefile cannot be found, the search path directories will be checked in turn to see if theycontain the source file. CrossStudio maintains two debug source file search paths:•Project session search path This path is set in the current project session anddoes not apply to all projects.•The global search path This path is set system wide and applies to all projects.The project session search path is checked before the global search path.