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

Bug 172 - Invalid initial states are not handeled gracefully
Summary: Invalid initial states are not handeled gracefully
Status: RESOLVED FIXED
Alias: None
Product: UPPAAL
Classification: Unclassified
Component: GUI (show other bugs)
Version: 3.5.7
Hardware: All All
: P1 normal
Assignee: Gerd Behrmann
URL:
Depends on:
Blocks:
 
Reported: 2005-07-05 21:25 CEST by Gerd Behrmann
Modified: 2006-02-20 19:50 CET (History)
0 users

See Also:
Architecture:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gerd Behrmann 2005-07-05 21:25:56 CEST 
If the initial state is not well defined, e.g. due to bad invariants or bad variable initialisers, then the GUI 
looses the server connection.

The expected behaviour is that such errors are shown in the editor, although this is difficult as the errors 
might only be present in some instances of a template.
Comment 1 Gerd Behrmann 2005-07-05 21:26:44 CEST 
Oops, wrong assignee.
Comment 2 Gerd Behrmann 2006-02-20 19:50:06 CET 
Support for this has now been added on the trunk. Out of range initialisers and
similar problems are reported like any other parse error. Ill-defined states due
to the invariants of the initial state being false are reported, but the error
is not attributed to any particular invariant: In the general case, the error
can be caused by a combination of invariants.