Menu
▾
▴
#518 Hosted stack behaviour.
On "hosted" systems, AROS code directly calls things on the host side (after obtaining pointers to relevant functions via hostlib)
This is a terrible design flaw and needs to be addressed ASAP. The main issue is that this results in "host" functions beaing called with the AROS stack still in use, having dire results.
One example of the consequences of this behaviour is using the host gl library. since we have no idea about the stack needs of the hosts gl components/drivers, or even how the host deals with the stack (expanding it/remapping it) our direct use of its functions results in undesired behaviour in the host code, and corruption on AROS's side.
It is impossible to quantify the damage this can cause on the host system, or in AROS.
IMHO hostlib needs to provide a trampoline function that calls the actual requested code, swapping in the hosts stack etc as appropriate.
ALL exisiting code calling the host (x11/sdl drivers/unixio) need to be adapted to call functions via this.
Last edit: Kalamatee 2016-08-08