Boundedness check broken for TACPN
Bug #1954699 reported by
Jiri Srba
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
TAPAAL |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
Open the referendum-
the boundedness check. It fails as the engine on the call returns:
Segmentation fault: 11
Changed in tapaal: | |
status: | New → Fix Committed |
To post a comment you must log in.
The boundedness check is still broken even with the updated engine. Now it returns that 0 tokens is enough to make it bounded (which is wrong). It wrongly parses the >4 information from the query.