Protect memory above MemoryLimit being nuked when starting a task
Detail: s/Wimp08s - Improve testapplication to detect situations where data is being stored above MemoryLimit, e.g. if a C app uses system() to issue *WimpTask Usually the CAO check will detect this kind of situation, except for the case where a single-tasking app issues *WimpTask - in which case the CAO will get reset to the Wimp module due to ModHandReason_Enter being used to get into USR mode so a temp parent task can be created Wimp_SlotSize checks MemoryLimit against ApplicationSpaceSize before allowing the wimpslot to be resized, so it seems to be a bit of an oversight that the task startup code wasn't doing the same Admin: Tested on BB-xM Fixes ticket #279: https://www.riscosopen.org/tracker/tickets/279 Version 5.39. Tagged as 'Wimp-5_39'
Showing with 33 additions and 20 deletions