Prevent changing the activity from a component's own thread #171
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch partially solves issue #141. It is not possible to change the activity of a component from within the component's thread because it would have to destroy itself afterwards.
RTT::TaskContext::setActivity()
logs an error and returns false in this case.RTT::TaskContext::forceActivity()
logs a fatal error.The debug log output during thread termination has been moved from the thread destructor to the
terminate()
method to fix logging during the destruction ofRTT::Activity
(see also 58cb4bb).