Fix #8, Remove unnecessary characters from memory dump event#79
Open
Fix #8, Remove unnecessary characters from memory dump event#79
Conversation
Contributor
Author
|
@thnkslprpt I reverted the original (#52) so we could move it to the next release. Does everything look good here? |
Contributor
Yes looks great Dylan. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Checklist
Describe the contribution
0xand trailing space around each byte from the dump event message.Testing performed
Build & Run + Unit Tests.
Expected behavior changes
Increases the number of bytes that can be dumped in the event message string dramatically (by around double, depending on the value that is set for
CFE_MISSION_EVS_MAX_MESSAGE_LENGTH).Contributor Info
@thnkslprpt