Closed Nielswps closed 3 years ago
I haven't seen that error before. Do you still have the diagrams that produced the Integer expected
error? If you zip the files and attach them to this PR, I'll take a look at the problem.
I am unable to recreate the error, after trying on both Windows and Ubuntu with two different sample projects, so I assume that it is no longer an issue. I will close this issue
The error is displayed whenever trying to run queries.
I have been looking into the exception generating the message, and it seems to originate from the parseInteger method within the Parser class (line 58). The method calls the nextToken method, which returns 2, causing the parseInteger method to throw the exception.
The exception is caught on line 155 in the Engine class and thrown as an EngineException.
All the classes mentioned above are part of the model.jar file located within the libs folder and originate from UPPAAL. The method called from H-UPPAAL causing the exception is located on line 150 in the UPPAALDriver class. The input is a UppaalSystem object, which is generated based on the HUPPAALDocument generated for the project. This also happens within the Engine class inside the model.jar and is assumed be handled correctly, hence the element closest to the exception handled by H-UPPAAL is the UPPAALDocument generated inside the HUPPAALDocument class.
I have also discovered that the 10. Semester project mentioned that H-UPPAAL was compiled using UPPAAL version 4.1.19 (from 2014). Using this version, a “Syntax error” is shown instead of the “Bug: Integer expected” error. This error is given within the parseProlog method inside the Parser class.