|Summary:||"Fatal error: null" when running a fastest diagnostic trace|
|Product:||UPPAAL||Reporter:||Lars T. Mikkelsen <ltm>|
|Component:||Engine||Assignee:||Gerd Behrmann <behrmann>|
Description Lars T. Mikkelsen 2005-04-15 11:15:13 CEST
Steps to reproduce: 1. In the attached model, insert the following query: E<> Girl1.knows_all and Girl2.knows_all and Girl3.knows_all and Girl4.knows_all 2. Select Options, Diagnostic Trace, Fastest from the menu 3. Press Check Result: Fatal error: null The server connection has been killed. Futhermore, ArrayIndexOutOfBoundsException and NullPointerException are thrown.
Comment 3 Robert Olesen 2005-04-23 11:51:39 CEST
The bug cannot be recreated in version 3.5.4 on windows (which narrows the possible location of the bug).
Comment 4 Gerd Behrmann 2005-04-24 19:40:13 CEST
On Linux with UPPAAL 3.5.5 I do see the exceptions, although I do not loose the server connection. I will investigate the problem further.
Comment 5 Gerd Behrmann 2005-04-24 20:01:34 CEST
Turns out that this is a problem in the serialization method for symbolic states: When finding the shortest trace, UPPAAL internally adds an extra clock to the model to keep track of the length (in time) of the trace. Unfortunately, the serialization method was not aware of this and as a result it also serialized this additional clock. A fix has been checked into CVS.