fix: log store only if it actually happened #1995
Merged
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.
Since 92e4f02 moved logging logic into
store_slow_pathfunction it has been logging stores even ifactually_storeparameter is false. Because of that logging is broken for all atomic instructions. Functionamocallsstore_slow_pathwithnullptrargument andactually_storeequal to false while callee usesreg_from_bytesindependently fromactually_storevalue All of that causes dereferencing ofnullptr. This commit logs memory access only if it actually happened.This bug was found while trying to execute some code with atomics with
--log-commitsoption (Made reproducer into a test in this commit). And getting segmentation fault. After rebuilding with address sanitizer got the following error: