Re: langwars - eu4.0 causeway prob (sorry)
- Posted by mattlewis (admin) Dec 02, 2008
- 1138 views
I got to the startup screen, pressed enter to enjoy a session of c ship destruction, and was then promptly chucked out to the command line, with lots of causeway probs.
I've been trying to work through this and its proving to be very difficult. My guess so far is that the Euphoria tasking mechanism is not working well. In any case, something is corrupting memory as it runs. Finding the culprit is difficult because adding any form of tracing into the program changes the program and thus seems to change where the problem lies.
Maybe someone else has some insights????
The previous problems with tasking revolved around the temporary code buffer in
static int **code[3];
It could be that Causeway doesn't like however Watcom implements this. You might try moving the declaration to outside of the function.
Matt
