[Main]
[Docs]
[Installs]
[Search]
[Team]
[Guestbook]
[Links]
WHDLoad's dumps and logfiles
Mainly for debugging purposes WHDLoad can create various dump and logfiles.
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 in the Slave structure). A memory dump will be
created if the DebugKey is pressed or after an
error the CoreDump button will be pressed. The name of the memory dump file
created 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 be overwritten. If the installed
program uses additional Expansion-Memory (ws_ExpMem), it is saved under the filename
".whdl_expmem".
The register dump contains the complete status of the CPU (including MMU), the
CIA and the Custom chips. Some CIA and Custom registers are not readable,
these are only contained in the dump file if a Snoop mode was active. The information will be
written to an ASCII file with some highlighting done using Escape sequences
(using CSI - Control Sequence Introducer, decimal 155). To view, a program which
supports Escape sequences is recommended (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 already exists, the dump will be appended - otherwise a new file will be
created.
The complete dump file is a
IFF file containing the information of all previously listed dump files. It is
intended to be used by other applications. The structure of the file is
described in an extra include file named whddump.i. Currently the
applications WHDLoadGCI (graphical coders interface) and SP (save picture) are reading the complete dump file. The
name of the complete dump file created is ".whdl_dump". The default location is
"PROGDIR:" but can be changed with the CoreDumpPath option. An existing file will
always be overwritten.
All disk accesses will be logged if the FileLog/S option has been activated. This feature
will be very useful to analyze the disk operations of the installed program
for debugging and optimizing purposes. 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. A
log entry shows the called function, a CRC of the read/written data, the
parameters and the result. WHDLoad will collect the log entries in an internal
LogBuffer/K/N . The buffer will be flushed on
exit and during making an entry if the buffer is full. The information will be
written to an ASCII file. The name of the dump file is ".whdl_log" (prior to
WHDLoad v18.0 it was ".whdl_filelog"). The default location is "PROGDIR:" but
can be changed with the CoreDumpPath
option. If a file with the same name already exists, the dump will be appended
- otherwise a new file will be created.
Starting WHDLoad version 18.0
it is possible to create additional custom log entries in the file ".whdl_log"
using the function resload_Log. The
entries can be formatted using a sprintf like format string and parameters.
Entries will be cached in the LogBuffer/K/N to
avoid switches to the operating system. For a large amount of entries the
LogBuffer should be increased accordingly. To get the log entries written the
option FileLog/S must be activated.
[Main]
[Docs]
[Installs]
[Search]
[Team]
[Guestbook]
[Links]