Fix invalid chunk size error #157
Open
Conversation
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
Under certain circumstances (including running the tests), gearshifft runs successfully but then fails during program finalization, showing an error: malloc_consolidate(): invalid chunk size This is due to the fact that boost unit test is linked (either statically or dynamically) but the single header variant is included everywhere. This fixes the error by including the correct boost unit test header for usage in linking scenarios. More information: https://www.boost.org/doc/libs/1_59_0/libs/test/doc/html/boost_test/usage_variants.html
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Under certain circumstances (including running the tests), gearshifft runs successfully but then fails during program finalization, showing an error:
malloc_consolidate(): invalid chunk size
This is due to the fact that boost unit test is linked (either statically or dynamically) but the single header variant is included everywhere.
This pull request fixes the error by including the correct boost unit test header for usage in linking scenarios.
More information: https://www.boost.org/doc/libs/1_59_0/libs/test/doc/html/boost_test/usage_variants.html