Possible Ring Buffer Fix #586
No reviewers
Labels
No Label
API Change
Breaking API Change
bug
build
cosmetics
Documentation
duplicate
feature
help wanted
hotfix
invalid
question
Refactor
Tests
wontfix
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: fsfw/fsfw#586
Loading…
Reference in New Issue
No description provided.
Delete Branch "eive/fsfw:mueller/possible-ring-buffer-fix"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Avoid memory leak if passed data is greater than maximum allowed size and overwriteOld iset set to true.
Fixed Unittests
WIP: Possible Ring Buffer Fixto Possible Ring Buffer FixAfter talk about this PR: There will be an update to this PR where the function will actually cut off the tail of a packet which is too large and write the remaining packet size (maximum ring buffer size) into the ring buffer if
overwriteOld
is set to true.During implementation of the updated functionality for the
overwriteOld
flag, it showed that theoverwriteOld
flag might not be handled correctly in some cases.Setting this PR to WIP until I figure it out.
Possible Ring Buffer Fixto WIP: Possible Ring Buffer FixWIP: Possible Ring Buffer Fixto Possible Ring Buffer Fix