Original report by Artho Cyrille (Bitbucket: 557058:d037361a-d6a1-4cae-80e0-7b1940bbc779, GitHub: cyrille-artho).
Currently, jpf-visual starts when JPF finishes. It would be nice to be able to incrementally view a trace of a running program, even though this would not work for debugging a failure.
Challenges are making all the data structures flexible enough to cope with a mutable trace, in particular with backtracking that may occur with JPF. (Perhaps refreshes should not be automatic with JPF, as backtracking could make existing choices for highlighting events obsolete.)
Original report by Artho Cyrille (Bitbucket: 557058:d037361a-d6a1-4cae-80e0-7b1940bbc779, GitHub: cyrille-artho).
Currently, jpf-visual starts when JPF finishes. It would be nice to be able to incrementally view a trace of a running program, even though this would not work for debugging a failure.
Challenges are making all the data structures flexible enough to cope with a mutable trace, in particular with backtracking that may occur with JPF. (Perhaps refreshes should not be automatic with JPF, as backtracking could make existing choices for highlighting events obsolete.)