-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allocator_may_return_null doesn't seem to be set to 1 when fuzzers are run under MSan #68
Comments
I'll take a look at this next week when I get back from break. |
I've just run into this issue. Even though
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I added a file to the seed corpus and it triggered an unreproducible MSan crash I reported in #67 (comment). By running
./infra/helper.py
I noticed that it failed because the allocator was out of memory. Issues like that are kind of ignored in ASan runs where allocator_may_return_null=1 is passed among ASAN_OPTIONS and propagate until real OOMs are hit, which is handled by the REPORT_OOMS setting.The text was updated successfully, but these errors were encountered: