Strange Memory behaviour with OS 3.1 on WinUAE/060/64MB config

[dissident]

When I boot the Workbench, run my demo and do writes to the RAM-Disk after my demo is finished, I get the guru shown on the screenshot if I use my WinUAE/060/64MB config. The Guru message in English: "Sanity check on memory list failed during AvailMem(MEMF_LARGEST)"

On my A1200/020 WibUAE config evverything works fine.

On my real A1200/060/64 MB and A1200/020 with OS3.18 everything also works fine,

Funnily if I run Mungwall on the WinUAE/060/64MB config before I start the demo, everything is also fine.

Maybe Thomas Richter knows what this is all about.

[Thomas Richter]

Something stomped on the memory, but where exactly might be hard to trace. Mungwall is pretty much outdated and has some issues. As classical memory debugger, I would suggest WipeOut, but if a MMU is available, MuGuardianAngel may help even better as it may be able to capture the access directly.

[dissident]

Originally Posted by Thomas Richter

Something stomped on the memory, but where exactly might be hard to trace. Mungwall is pretty much outdated and has some issues. As classical memory debugger, I would suggest WipeOut, but if a MMU is available, MuGuardianAngel may help even better as it may be able to capture the access directly.

I will check it with these tools.

[Phantasm]

Originally Posted by Thomas Richter

Something stomped on the memory, but where exactly might be hard to trace. Mungwall is pretty much outdated and has some issues. As classical memory debugger, I would suggest WipeOut, but if a MMU is available, MuGuardianAngel may help even better as it may be able to capture the access directly.

There great info. I am still using mungwall as I was not aware of wipeout

[dissident]

For those who are intrested in it.

I found the bug in my code. The guru was caused by AllocBitmap() due to the fact that my allocated memory block was too small and I did blitter and cpu operations outside the allocated memory block.