When using a global const and a local variable with the same name, trying to read its value in the process (when trying to simulate or model check) only leads to a "Server connection lost" error. I think it would have cost me not so much time to figure my fault out, if there would have been a "better" error reporting (well, I know that it's not a syntax error)
The behaviour you describe is a server crash due to some internal fault. I have not been able to reproduce the error from your description. Could you please attach the model triggering this bug to the bug report or email it to me directly. Thanks.
Created attachment 81 [details] Example System When (incorrectly) using a clock as an index for an array, syntax check is ok, but using the model leads to "Server connection lost". It's not a bug, but better error reporting would be great. (My fault was, i forgot to delete a (local) clock and introduced a global const with that name, so when i tried to use the const as array index, uppaal tried to use the clock, which obviously couldn't work)
Thanks, I see the problem now. It is most certainly a bug: The "error message" you describe means the verification server crashed and that should never ever happen. The fact that the crash was triggered by a type error in the input model does not change this. Will be fixed before the release of alpha 3. It seems that the type of array indices is not checked at all.
Fixed on the trunk (revision 1334).