Attempting to process a .spx file results in an error message
"Error reading savetst.spx"
Spitbol's memory initialization is broken for .spx files and will require a rework of how memory is initialized and managed.
There are assumptions about how the C stack and how memory is allocated that are currently incorrect with current C and Linux environments
Instead of trying to perform low level memory management within Spitbol (vis sbrk and brk), just use C's memory allocation routines (e.g. malloc -- which is being done anyway for some memory regions).
Attempting to process a .spx file results in an error message
"Error reading savetst.spx"
Spitbol's memory initialization is broken for .spx files and will require a rework of how memory is initialized and managed.
There are assumptions about how the C stack and how memory is allocated that are currently incorrect with current C and Linux environments
Instead of trying to perform low level memory management within Spitbol (vis sbrk and brk), just use C's memory allocation routines (e.g. malloc -- which is being done anyway for some memory regions).