Simulation of trace is incorrect in some situations
Bug #622134 reported by
Morten Jacobsen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| TAPAAL |
Fix Released
|
Critical
|
Kenneth Yrke Jørgensen | ||
Bug Description
steps to reproduce:
1. Open attached net
2. obtain trace with "optimised standard" for the query EF(p1 = 2 and p2 = 2)
3. Step forward in the trace
On the last step, a token is not consumed from p0, but tokens are produced in p1 and p2.
This affects TAPAAL 1.3 also..
Related branches
Revision history for this message
| Morten Jacobsen (mortenja) wrote | #1 |
| Changed in tapn: | |
| status: | New → Confirmed |
| assignee: | nobody → Kenneth Yrke Joergensen (yrke) |
| importance: | Undecided → Critical |
Revision history for this message
| Kenneth Yrke Jørgensen (yrke) wrote | #2 |
| Changed in tapn: | |
| status: | Confirmed → In Progress |
Revision history for this message
| Kenneth Yrke Jørgensen (yrke) wrote | #3 |
| Changed in tapn: | |
| status: | In Progress → Fix Committed |
| Changed in tapaal: | |
| status: | Fix Committed → Triaged |
| status: | Triaged → Fix Released |
To post a comment you must log in.
The problems has been traced back to an error with the trace parsing when
using the "optimised standard" reduction.
Working on a fix...