This is the error submitted to bug-uppaal by Hans Pettersson - Wed, 12 May 2004 16:38:02: The problem is that it seems to write to an undefined memory area (see below.) --------------------------- server.exe - Application Error --------------------------- The instruction at "0x00434287" referenced memory at "0x01655380". The memory could not be "written". Click on OK to terminate the program Click on CANCEL to debug the program --------------------------- OK Cancel --------------------------- But as far as we can see there should be no such error. If you run our program as it is sent, then the error will appare in the scheduler template, state S3, just after a few sec in random mode. The problem seems to have something to do with the "Process_ID" variable. Can you please take a look at our program and see if this is a bug or just something we have missed? Best Regards Hans Pettersson
Created attachment 20 [details] The model that makes uppaal crash
Confirmed.
This bug is triggered by an out of array condition in a synchronisation label of the model. The exception that is thrown as a consequence seems to corrupt some of the stack (but only on Windows). My guess is that this is a compiler bug.
Created attachment 21 [details] Smaller test case
I have created a small test case that triggers this problem in the compiler and submitted it as a bug to the mingw people. Let's see what they do about it.
Here is a link to the bug report at mingw: https://sourceforge.net/tracker/index.php?func=detail&aid=966724&group_id=2435&atid=102435
Reduced severity to major. Seems that the mingw people finally noticed my bug report, but no ETA for a fix yet.
The fix for bug 170 also fixes bug 102. The compiler is still buggy, but we no longer do dynamic allocation on the stack at this place in the code, thus we are no longer affected by the bug.