Restart trace not working
At this time, an assert() has been added to inform us of execution flow error and this assert is triggered when restarting a trace. The enabled flag needs to be put in the global UST session and removed from the UST app session where it is basically not used.
Updated by David Goulet over 8 years ago
- Status changed from New to Resolved
Fix with commit f848c3eb8a294665ea333a0d5244bd5adba8277c
The started flag must be set as soon as possible in the start trace function since if the start fails, it is still consider started for the code logic.
The enabled flag will be fix later on and does not trigger any issues at this stage.