After latest updates from time to time i got various strange crash on diskboot.config, for example today i got one playing GLQuake
Quote:
Crash log for task "glquake" Generated by GrimReaper 53.5 Crash occured in module diskboot.config at address 0x01821674 Type of crash: DSI (Data Storage Interrupt) exception
i think there is something wrong Tony.. i'm having same problems on diskboot with all beta updates too and on different exe (also Elwood is having the same problems..)
But my crash log pointed to an offset in the kernel so, in my case, it might not be related to diskboot.config at all. I filled a bug report for my case.
Does not the MMU control if memory block is executable or not. A text file should not be executable, the CPU does not know the different between text and operation codes, they are hex values after all.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
There is a Kickstart component called "diskboot.kmod", maybe that calls itself "diskboot.config" when running, or spawns a task that calls itself that.
If I weren't so busy (Read: lazy), I could look up the sources and find out. But look at it this way: when your program crashes in Exec, you don't blame Exec for the crash, you blame your program, don't you?
In this case, Quake is calling a newlib function that ends up in a crash. It's most likely that the crash is quake's fault. It is probably caused by some old coding trick that used to work back in the old days, but has been made illegal these days.
I think this is a new problem in IDOS->FindTrackedAddress(). For one thing, try and look at the crashlog in the first post: The bottom most entry says "GrimReaper" at addr 0x0000000", which is obviously not correct. When working with db101, I get all sorts of senseless output when giving address 0x0.
For one thing, try and look at the crashlog in the first post: The bottom most entry says "GrimReaper" at addr 0x0000000", which is obviously not correct.
I got the same crashlog running Timberwolf-RC3 in diskboot.config & GrimReaper at 0x0000000. Mine was an ISI exception crash. My hardware is an A1XE-G3 OS4.1 update6 (uptodate).