This issue tracker is closed. Please visit UPPAAL issue tracker at Github instead.

Bug 227 - Incorrect evaluation of array parameters
Summary: Incorrect evaluation of array parameters
Status: RESOLVED FIXED
Alias: None
Product: UPPAAL
Classification: Unclassified
Component: Engine (show other bugs)
Version: 3.6 Alpha 1
Hardware: All All
: P1 major
Assignee: Gerd Behrmann
URL:
Depends on:
Blocks:
 
Reported: 2005-11-22 13:16 CET by Gerd Behrmann
Modified: 2005-11-22 16:35 CET (History)
1 user (show)

See Also:
Architecture:


Attachments
Test case. (2.12 KB, application/xml)
2005-11-22 13:21 CET, Gerd Behrmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gerd Behrmann 2005-11-22 13:16:06 CET
I got the following report from Franck Cassez:

I noticed a strange behavior in the UPPAAL alpha release
(which is good because it is an alpha release ...)

Attached is the file I used. I used the MacOSX versions
of UPPAAL, 3.4.11 and 3.6 alpha.

	The problem:
		1) the guard in automaton node1 is a bool array to1[i]
		This array is initialized in the decls to {0,0,0,1}
		2) in 3.4.11, it is evaluated correctly (in the simulator);
		in the alpha release, the evaluation for i=0 seems to
		give "true" for to1[0] (in the simulator), but ... to1[0]=0

In the end, the simulation is different in the two versions. And I think
3.4.11 is the correct :-)
Comment 1 Gerd Behrmann 2005-11-22 13:21:02 CET
Created attachment 74 [details]
Test case.
Comment 2 Gerd Behrmann 2005-11-22 16:35:38 CET
A fix is in CVS.