Fix heap buffer overflow for string_match
benchmark when NO_MMAP
flag is used.
#10
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.
What is this PR doing:
Fixes #9
This PR adapts the buffer allocation for the
string_match
benchmark when theNO_MMAP
flag is set to eliminate the heap buffer overflow detected byASan
.How to test this PR:
Compile the benchmarks with a patch that enables the
NO_MMAP
flag andAddressSanitizer
(ASan
):Retrieve the inputs for the
string_match
benchmark:Run the
string_match
benchmark and observe the output ofASan
:With the change included in this PR,
ASan
does not report any heap buffer overflow error.Tested on:
OS:
Ubuntu 22.04.4 LTS
Kernel:
6.2.0-39-generic
gcc:
11.4.0