Jo Even Skarstein wrote:
As this "bug" has only been observed in Thing I'd say that Thing was already broken. It just worked by coincidence. The fact that it doesn't happen in 1.29 indicates that there indeed was a bug in Thing, and that it has been fixed. So I don't think it's necessary to spend more time on this.
Maybe, or maybe not.Thing 1.27 could be the victim of some random memory overwrite (such as the ones that can occur if there are register problems in the GemLib).
This is very serious.Running FreeMiNT with memory protection enabled could provide additional information. However I don't know if illegal memory accesses can be detected from kernel modules.
-- Vincent Rivière