Summary: | NullPointerException in simulator, does not update state information afterwards | ||
---|---|---|---|
Product: | UPPAAL | Reporter: | Marius Mikučionis <marius> |
Component: | GUI | Assignee: | Gerd Behrmann <behrmann> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 4.0.1 | ||
Hardware: | PC | ||
OS: | Linux | ||
Architecture: | |||
Attachments: |
model to reproduce an exception in simulator
Smaller test case |
Description
Marius Mikučionis
2006-07-12 19:21:48 CEST
Created attachment 107 [details]
model to reproduce an exception in simulator
*** This bug has been marked as a duplicate of 333 *** The behaviour described above does not depend on selecting 'shortest trace' (in contrast to what one might expect when the report explicitly states selecting 'shortest trace') - 'some trace' will also do. Thus the problem is unrelated to bug 333. Created attachment 110 [details]
Smaller test case
I have attached a test case. The liveness checker does not need to be involved. Indeed, the trace does not need to come from the model checker to reproduce the problem. In the attached model, take the enabled transition and click on that transition in the trace: Boom! The bug is in the function which selects the transition in the list of enabled transitions when clicking on a transition in the trace: The function does not deal correctly with transitions with target states not satisfying the invariant. Fixed on the 4.0 branch from rev. 2483 and on the trunk from rev. 2482. |