[3844] Ignore asan warnings (clang) #15
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
…reduce memory consumption.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
2022-06-20T22:42:42Z CathalT
Wanted to test out my WSL dev environment with Visual Code so took a crack at some of the address sanitizer warnings
1.) Added function attribute to ignore false unsigned int overflow warnings which fixes:
nanocurrency/nano-node#3658
nanocurrency/nano-node#3659
2.) Added blacklist file for Clang Address Sanitizer.
Also when running Address Sanitizer with core_test aborts in a couple of places:
It doesn't like that network_params is a reference and it is being accessed on different threads.
Is this a known issue or should I create a new issue?