WHDLoad's dumps and logfiles

Mainly for debugging purposes WHDLoad can create various dump and logfiles.

Memory dump

A memory dump is the whole memory used by the installed program written to a file, the size of the dump depends on the installed program (it is equal to the value of ws_BaseMemSize from the slave structure), a memory dump will be created if the DebugKey is pressed or after an error the CoreDump gadget will be activated, the name of the created memory dump file is ".whdl_memory", the default location is "PROGDIR:" but can be changed with the CoreDumpPath option, an existing file with the same name will always overwritten.

Register dump

The register dump contains the complete status of the CPU (including MMU status) at the moment of interrupting, some WHDLoad variables and internals, the values of the Cia chips as far as readable (not included are the alarm values of the 24-bit timers and the int-masks because they are not directly readable) and all readable Custom registers, if a Snoop mode is active also all by the CPU written Custom registers are included.
The informations will be written to an ASCII file, some highlighting will be done using Escape sequences (using CSI - ControlSequenceIntroducer, decimal 155), therefore a text-displayer which supports this is recommend (e.g. More, MuchMore, Multiview, ...), the name of the dump file is ".whdl_register", the default location is "PROGDIR:" but can be changed with the CoreDumpPath option, if a file with the same name does already exist the dump will be appended otherwise a new file will be created.

File access log

All disk accesses will be logged if the FileLog option has been activated. this feature will be very useful to analyze the disk operations of the installed program for debugging and optimizing purposes, it is also useful to simulate and verify the operation similar to a low memory situation where WHDLoad can't cache any files or disk images.
The following resload function will create an entry in the log file: Each file access via the functions above creates one line in the log file, the line identifies the called function and all the parameters.
The informations will be written to an ASCII file, the name of the dump file is ".whdl_filelog", the default location is "PROGDIR:" but can be changed with the CoreDumpPath option.