FAQ-0903 How do I use loader tracing to investigate "Not found" problems on target hardware?


FAQ-0903 How do I use loader tracing to investigate "Not found" problems on target hardware?

» Symbian OS » Developer Knowledgebase » FAQ-0903

Classification:	C++	Category:	Development
Created:	07/18/2003	Modified:	10/10/2003
Number:	FAQ-0903
Platform:	Symbian OS v7.0s

Question:
I have a problem which only shows up on target hardware, not on the emulator. When I launch a particular part of an application I just get a dialogue saying "Not found". Assuming this is caused by a missing executable, is there any tracing in the Symbian OS loader which could give me clues about which file isn't there?

Answer:
Run the EShell.EXE application and type the command sequence:

TRACE /L 80000000

This will enable loader tracing through the normal RDebug output, which you should capture for later analysis.

Now reproduce the problem (exiting from EShell if necessary), and then look through the generated trace output. For example, these lines were in a log obtained for a ROM which did not contain ESDRV.PDD and produced a "Not Found" dialogue when trying to create a new alarm in the Agenda application.

Failed to load ESDRV.PDD (return 0 or -1)
LoadCodeSeg returns -1

Note that this requires a debug build of the loader, so will only work with Devkit or similar environments.