Debug Log Output

G

Grotfang

Developer
I have all five options checked in the (debug) preferences. When I clicked Start Debug Log I expected internal function calls to be recorded. They weren't. The output I got from trying to adventure (while drunk) Trick-or-Treating was as follows:

Code: 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
             KoLmafia r8159, Windows 7, Java 1.6.0_17
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Please note: do not post these logs in the KoLmafia thread.  If 
 you would like us to look at the log, please instead email logs 
 to veracity@hambo.com using the subject "KoLmafia Debug Log" 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Timestamp: Fri Feb 19 23:53:23 GMT 2010
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=


Validating adventure sequence...
Requests complete.

You are too drunk to continue.

I get the same output if I uncheck all the preferences too. Is this the expected behaviour?

Basically, I was trying to track down why mafia thinks it can't trick or treat when falling down drunk, and thought a debug log would help me do that. It didn't.
 
jasonharper

jasonharper

Developer
The primary thing recorded by a debug log is server interactions - and there were none in this case, mafia denied the request itself.

A complete log of all internal function calls would be ridiculously large - some functions get called millions of times during normal operation! That's more in the realm of an external Java debugger or profiler, anyway (as an external tool, they can more easily deal with issues like not logging the calls to the function that logs all the other function calls...).
 
You must log in or register to reply here.
Top