-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Correct notes on CFE_FS_BackgroundFileDumpRequest #1703
Comments
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Jul 23, 2021
Update notes to better clarify that the meta object must persist for the duration of the dump operation, which occurs in another task, so it must not be on the stack.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Jul 23, 2021
Update notes to better clarify that the meta object must persist for the duration of the dump operation, which occurs in another task, so it must not be on the stack. Also update documentation for background even callbacks to better clarify arguments and expectations of the implementation.
jphickey
added a commit
to jphickey/cFE
that referenced
this issue
Jul 23, 2021
Update notes to better clarify that the meta object must persist for the duration of the dump operation, which occurs in another task, so it must not be on the stack. Also update documentation for background even callbacks to better clarify arguments and expectations of the implementation.
astrogeco
added a commit
that referenced
this issue
Jul 29, 2021
Fix #1703, update docs for CFE_FS_BackgroundFileDumpRequest
paulober
pushed a commit
to paulober/cFE
that referenced
this issue
Aug 1, 2021
Update notes to better clarify that the meta object must persist for the duration of the dump operation, which occurs in another task, so it must not be on the stack. Also update documentation for background even callbacks to better clarify arguments and expectations of the implementation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The notes for this API say "not on heap" when it really should say "not on stack"
To Reproduce
If buffer is allocated on the stack and object goes out of scope before background job finishes, random unpredictable behavior occurs, as in PR #1673.
Expected behavior
Correct comment.
System observed on:
CI
Additional context
Fundamental requirement is that object must persist for the time the background job runs. So stack is likely a problem, heap is OK as long as it isn't freed before task is done.
Reporter Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: