Skip to content
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

Fix a potential crash in TimeCache::findClosest #592

Merged
merged 1 commit into from
Mar 23, 2023

Conversation

clalancette
Copy link
Contributor

That is, make sure to check that the error_code passed in is not NULL before assigning to it.

This was introduced in #586 . @roncapat FYI.

That is, make sure to check that the error_code passed
in is not NULL before assigning to it.

Signed-off-by: Chris Lalancette <clalancette@gmail.com>
@clalancette
Copy link
Contributor Author

CI:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Windows Build Status

@clalancette clalancette merged commit 7afeb6c into rolling Mar 23, 2023
@delete-merged-branch delete-merged-branch bot deleted the clalancette/fix-potential-crash branch March 23, 2023 20:39
@clalancette clalancette mentioned this pull request May 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants