Alan Hourihane wrote:
I'm pretty sure I have memory protection enabled here when I did the test. Why don't I see the problem ??
I don't understand exactly when it becomes visible, because I have very limited knowledge about memory protection settings. The only concrete fact is I have an ARAnyM disk image where the tst.tos binary crashes.
This is a problem for the early stack. The bug was never triggered before, because I guess there was no trap call from the early stack. In my latest patch for the startup code, I added a Ssystem() call very early on the early stack, so any programs built with the current CVS MiNTLib crashes before main() on systems (like mine) where the bug is visible.
MiKRO, that reminds me the strange problems you experienced when the system is going out of memory. I don't know if it is related or not.
-- Vincent Rivière