This repository has been archived by the owner on Nov 22, 2023. It is now read-only.
Ready code for sanitizing #200
Closed
Conversation
This file contains 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
agutenkunst
suggested changes
Oct 9, 2019
|
Also please resolve the conflict, afterwards I would be open for merging |
|
Continued in PR #281. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Make code ready for sanitizing.
In order to do that, I firstly fixed some bugs which are shown by the the clang compiler. Consequently, I added the CMake flags needed to active the different sanitizers. The sanitizer flags are all off by default. Only one sanitizer flag can be activate at any time. In order to use the different sanitizer, the compiler has to be switched to the clang compiler. See here how to do this. If you now run the different tests with the different sanitizer, you will see some errors. Try it out and have fun ;)