Sad but true - for multiple reasons it is nowadays quite a rare situation that I launch an emulator to do S60 development or debugging. Last week I had to do some debugging to solve a weird email problem on S60 devices; because the problem was with the native email application, I configured the email account to emulator, enabled logging, studied the logfiles and understood what was wrong. After had done that I understood that maybe this logging trick isn’t a well-known tool for developers, at least a quick search to developer resources didn’t find anything.

If you trace the epoc.exe application with Filemon or other similar tools, you will notice that emulator tries to access many directories under $(EPOCROOT)epoc32\winscw\c\logs but fails to write data there because those directories don’t exist by default. If you create directories by hand, you will see logging data appear there for many platform applications. Sometimes that log data makes sense for a developer without the platform source code, sometimes not. If you want to try yourself, create directories like AOEmail, AOMan, Browser, certmanui, connectiondialogs, EMail, java, MCe, mediator, scard, swlstoken, tlsprovider, UiLib... Sure, that list is not complete - trace the emulator process and try to find which directory to create for more data. 

//Harri

--