Bug 200 - Crash using parameter constant in int range for variable with default initialization
Summary: Crash using parameter constant in int range for variable with default initial...
Status: RESOLVED FIXED
Alias: None
Product: UPPAAL
Classification: Unclassified
Component: Engine (show other bugs)
Version: 3.5.9
Hardware: PC Linux
: P2 normal
Assignee: Gerd Behrmann
URL:
Depends on:
Blocks:
 
Reported: 2005-09-22 11:56 CEST by Leonid Mokrushin
Modified: 2005-09-22 12:27 CEST (History)
0 users

See Also:
Architecture:


Attachments
Test case (671 bytes, application/xml)
2005-09-22 12:24 CEST, Gerd Behrmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Leonid Mokrushin 2005-09-22 11:56:43 CEST
When an integer in defined in a template as follows

Template name:      MyTemplate
Parameters:         const int bound
Declarations:       int[0,bound] MyVar;
Process assignment: MyProcess:=MyTemplate(2);
System declaration: System MyProcess;

the GUI says "server connection lost" and verifyta reports "CAUGHT EXCEPTION:
InterpreterException". The problem can be worked around by making declaration
look "int[0,bound] MyVar = 0". Both Linux and Windows engines have the same
effect. The problem does not appear if bound is defined as local constant.

Second problem: the "out-of-range" error for "int[0,bound] MyVar = -1" is
reported in GUI as "Word expected".
Comment 1 Gerd Behrmann 2005-09-22 12:24:50 CEST
Created attachment 56 [details]
Test case
Comment 2 Gerd Behrmann 2005-09-22 12:27:14 CEST
The bug is already fixed in CVS.