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

Bug 650 - server crash with Segmentation fault
Summary: server crash with Segmentation fault
Status: ASSIGNED
Alias: None
Product: UPPAAL ECDAR
Classification: Unclassified
Component: Engine (show other bugs)
Version: 0.10
Hardware: PC Linux
: P5 normal
Assignee: Marius Mikučionis
URL:
Depends on:
Blocks:
 
Reported: 2018-03-28 13:58 CEST by Marius Mikučionis
Modified: 2018-06-25 11:56 CEST (History)
1 user (show)

See Also:
Architecture:


Attachments
std input stream to server (18.18 KB, text/plain)
2018-03-28 13:58 CEST, Marius Mikučionis
Details
A zip file with the debug files gotten from the Socketserver, NB the model used there is the University example, anyhow same problem occurs (32.95 KB, application/zip)
2018-03-30 09:56 CEST, Rene Mejer Lauritsen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marius Mikučionis 2018-03-28 13:58:02 CEST
Created attachment 323 [details]
std input stream to server

The server crashes when handling requests from model.jar API.
The input to server is attached.
Comment 1 Rene Mejer Lauritsen 2018-03-30 09:56:23 CEST
Created attachment 324 [details]
A zip file with the debug files gotten from the Socketserver, NB the model used there is the University example, anyhow same problem occurs

The whole crash happens when calling the getTransitions() in the Engine class in the Model.jar. 
Here I have used the Model.jar and Uppaal.jar which are included in the Ecdar0.10 tool. The parameters I pass to the method is the system, which has been generated by the same Model.jar, and the initial symbolic state, gotten from getSymbolicInitial().

In the Zip file, there are examples of how I use the Model.jar, in the EcdarDriver.java and EcdarTraceHandler.java. It is in the EcdarTraceHandler.java where getTransitions() is called.

It also has to be mentioned that I do not have problems with regards to executing queries.