google / google/clusterfuzzlite

allocator_may_return_null doesn't seem to be set to 1 when fuzzers are run under MSan

Open
#68 2 comments 0 reactions 1 assignee Claimed by @jonathanmetzman View on GitHub
Dominant language
No language data
Stars
536
Forks
54
PR merge metrics
No merged PRs in 30d

Description

I added a file to the seed corpus and it triggered an unreproducible MSan crash I reported in https://github.com/google/clusterfuzzlite/issues/67#issuecomment-995356807. 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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.