Full logging sometimes not activatable

[Reth]

Hi again,

in order to log until system freezes I tried to setup logging in WINUAE GUI.
But mostly when choosing winuaelog.txt path field stays empty and everything to get it filled is greyed out. I only can use winuaebootlog.txt which does not contain any logging after booting - even if I tick full logging.

How can I activate the full logging into file again? I already was able to recently.

Any hints highly appreciated!

Bye

[DamienD]

Errrrr, possibly tick the box "Enable full logging" before starting emulation?

[Reth]

As already mentioned => Enable Full logging does not change anything (see screenshot)!
I only can use winuaebootlog.txt in the selection but also full loggin does not log into winuaebootlog.txt after booting!

Unfortunately now WinUAE always crashes completely when I start Codebench inside AOS4.1FE! If I shall use the debug version please let me know.

[Foebane]

It's not just a case of ticking "Enable full logging" and then start the emulation, but when you reach the point in the emulation where the problem occurs, you hit F12 and click on "Save all" under "Debug logging" to output the logs to a zip file which you can then upload to this forum.

[Reth]

OK, understood. But how can I get full logging into winuaelog.txt back too?
And as for the recent problems entire WinUAE crashed several times - so no chance to hit F12 and save something!

[DamienD]

Start WinUAE, load your configuration, change to "Paths", just tick "Enable full logging" (don't touch anything else / dropdown menus etc.) and run until you have the issue, then wait another 5 seconds afterwards.

Quit WinUAE, attach logs here

[emufan]

Originally Posted by DamienD

Quit WinUAE, attach logs here

I've seen those crashs too, it's not the emulation, it is the emulator that does crash.
no way to access the F12 gui and save the logs.

[DamienD]

Originally Posted by emufan

I've seen those crashs too, it's not the emulation, it is the emulator that does crash.
no way to access the F12 gui and save the logs.

Who said anything else about having to press <F12> and then save the logs for stuff to be captured in the "winuaelog.txt" file?

If WinUAE crashes then the logs should still show this; plus when further investigation is needed then Toni will ask for dump file.

[emufan]

Originally Posted by DamienD

Who said anything else about having to press <F12> and then save the logs for stuff to be captured in the "winuaelog.txt" file?

If WinUAE crashes then the logs should still show this; plus when further investigation is needed then Toni will ask for dump file.

at the moment I have no test case, but I assume winuae wont write the logs after it does crash.
there was no crash dump after those crashs.
one possible way, maybe, using the "open log window" and try to copy the content after winuae goes on suicide.

[DamienD]

Originally Posted by emufan

at the moment I have no test case, but I assume winuae wont write the logs after it does crash.

No, probably not but the last captured line should be the trigger / cause hopefully.

Originally Posted by emufan

there was no crash dump after those crashs.

...then over to Toni for next steps

Originally Posted by emufan

one possible way, maybe, using the "open log window" and try to copy the content after winuae goes on suicide.

Yes i.e. start WinUAE with -log switch via command line *may* help.

[emufan]

Originally Posted by DamienD

No, probably not but the last captured line should be the trigger / cause hopefully.

but could be just the filename with filezize zero.
possible winuae does buffer the whole log and will save only on exit or "save logs" instruction.

Yes i.e. start WinUAE with -log switch via command line *may* help.

it does open an extra window aswell, but this may help to get the latest debug lines.

[Foebane]

Perhaps the winuae.exe file has become corrupt? Maybe re-downloading the relevant zip from the WinUAE website and overwriting the original exe will fix things?

[emufan]

Originally Posted by Foebane

Perhaps the winuae.exe file has become corrupt?

unlikely. In my case I had a problem with picasso96 installation.
winuae did crash when booting in a RTG workbench.
after disabling some things in my workbench setup, the problem disapeared.
this was with the very same version of winuae.

[Toni Wilen]

Log with "winuae.exe -log -logflush" may help (logflush = force cached data to the disk after each line) but generally crash debugging requires crash dump file.