Wrong trace in verifypn engine

Bug #1825048 reported by Jiri Srba on 2019-04-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
TAPAAL
Critical
Peter Gjøl Jensen

Bug Description

Open the attached net and verify the query. The returned trace has only
4 transitions and clearly does not bring us to a marking where count=0.
This is broken even without any reduction/simplification techniques.
If you change the query to have count=1 then it works.

Related branches

Jiri Srba (srba) wrote :
Changed in tapaal:
status: New → In Progress
Changed in tapaal:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers