Getting C1-C5 settings from .whdl_dump

[paraj]

Is there an easy way to get the user's settings for the "custom" values from a/the dump file(s) [.whdl_dump and so on]? From reading whddump.i they don't seem to be saved directly. I guess some/most of them can be inferred based on the memory contents, but that's a bit of work.

Asking because we (read: I) may have gone bit beyond what they were meant for in the TFX slave, and it'd be convenient if there was an easy way of checking what settings were used.

[StingRay]

I don't think it's trivially possible to get these settings from a dump file. However, why does it need to be the dump file? I suppose you have access to the slave source, in that case you could add some debug code that would simply save the taglist that contains all the CUSTOMx settings and the relevant values and then inspect the (very small) saved memory block. If the CUSTOMx tooltypes are parsed without the help of taglist, it would still be possible, but would require slightly more code to do so.

I may not have understood your use case correctly though, so it may be possible that my suggestion doesn't help you. If that's the case, maybe you can provide some more details on what you want to achieve?

[Wepl]

There is no generic way to retrieve these values.
Normally they are only stored inside WHDLoad's memory.
But, as StingRay wrote, if you retrieve them via resload_Control and store them without overwriting them you can get them from the dump files. It's your choice to store them in BaseMem, ExpMem or the Slave.
Starting WHDLoad 18.9 all options are dumped in the .whdl_trace file if option TRACE is active.
I will add dumping these to the .whdl_dump file in the next release. This was anyway planned.

[paraj]

Thanks, a tag list that I can easily find later in slave mem sounds like a good idea. Will do that going forward

Just to explain why I asked: For TFX the CUSTOMx settings allow switching between 4 different executables, auto-selecting a pilot, replacing drawing routines etc., all of which could make difference when trying to track down the cause of a crash. The user (sometimes myself) may not remember the exact settings used when the crash dump was created, so being able to get them automatically would help. The chosen executable is usually in the termination message (since segtracker is enabled), but not always, and most of the other settings I can infer from what was patched, but it's a bit tedious.

[jotd]

Storing the memory map of the machine and its CPU/FPU ECS/AGA would be nice.

With emulators we can have weird configurations but a 68010 config would tell a lot for instance

[Wepl]

the memory of the host system is in the .whdl_trace file
the relevant memory for whdload is in the .whdl_register
there is also cpu/fpu type:

 attn=FF(60,82) fc=-1 kn=0 zpt=-1 ep=0 ei=0
setcpu=3B3D(SS,BC,SB,DC,IC,SCB,ECB,BNC)

attn are the AttnFlags, with cpu type
setcpu gives the cache settings
ss = superscalar
bc = branch cache
sb = storebuffer
dc = data cache
ic = instruction cache
then follows cache mode of the memory Slave, Exp, Base with CB=CopyBack and NC=NonCachable
chipset OCS/ECS/AGA is currently not printed as WHDLoad is also not detecting this

do you want any more infos?

[jotd]

no it is enough!

[Wepl]

fc = function code used on 68030 for transparent translation (mmu)
zpt = detected remap of first pages via mmu on the host (68060.library)
ep = amount of emulated privilege violations (move sr,dx from user mode)
ei = amount of emulated integer instruction on 68060 (movep, cmp2, mul/div)