Crash with WinUAE 3.0.0

[tero]

Hi,
WinUAE crash/freeze when i try to compile sources with AmiBlitz.

Log says 'JIT: Can't handle access'. With JIT off it says 'CPU halted: reason = 3'
Both freeze winuae in the same moment.

EDIT: In 2.8.1 a guru (8000 000A) is shown. This is correct in this case

[Toni Wilen]

Originally Posted by tero

Hi,
WinUAE crash/freeze when i try to compile sources with AmiBlitz.

Log says 'JIT: Can't handle access'. With JIT off it says 'CPU halted: reason = 3'
Both freeze winuae in the same moment.

Sounds like common Amiga-side problem of too small stack size. Running "stack 100000" before running crashing program should help.

(HALT shouldn't freeze it, only waits for reset. HALT = CPU stopped due to double fault)

EDIT: In 2.8.1 a guru (8000 000A) is shown. This is correct in this case

I don't think so. Your memory layout is now different (Z3 RAM in official location, this is now preferred if possible since 3.0, reduces problems with PPC operating systems. You switch to old mode by setting memory panel Z3 mapping to UAE)

[tero]

Raising stack/old Z3 mapping makes no difference. See below, but i would prefer a guru instead the freeze.

Anyway, the matter has resolved itself:
In the meantime i figured the whole Guru was my fault, endless loop inside an include i used in all sources i tried.

[Dunny]

Had one crash with the new WinUAE also - hard lock up, window doesn't respond to any input (no F12 to bring up UI, RMB doesn't release the mouse) after an error box. This was with A1200 4MB quickstart option trying to get NIALL to run.

I'll see if I can get it reproduced and gather logs.

D.

[Nut]

Hate to complain but JIT on-the-fly switch ON crashes 3.0.0. Have to boot JIT ON for it to work. Then you can switch off/on without problems. It worked with previous versions, sort of, some versions did

[Toni Wilen]

I think last two posts don't include enough information to be any use..

--

HALT status when program attempts to execute code from unexisting memory is now correct behavior. It is unrecoverable anyway and makes debugging easier, just check the log, getting to OS crash handler (if you are fortunate enough) will only get useless crash information.