Skip to content
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

How to disable memory leaks detection? #73

Closed
RazrFalcon opened this issue Mar 6, 2017 · 4 comments
Closed

How to disable memory leaks detection? #73

RazrFalcon opened this issue Mar 6, 2017 · 4 comments

Comments

@RazrFalcon
Copy link
Contributor

I'm getting:

SUMMARY: AddressSanitizer: 433 byte(s) leaked in 3 allocation(s).
INFO: a leak has been found in the initial corpus.
INFO: to ignore leaks on libFuzzer side use -detect_leaks=0.

I don't know is it are real leaks because it triggered by Rc::new().

PS: maybe this issue should be treated as "How to pass custom flags to libFuzzer", which is not done yet (AFAIK).

@nagisa
Copy link
Member

nagisa commented Mar 6, 2017 via email

@RazrFalcon
Copy link
Contributor Author

Thanks. It works. Maybe it should be added to readme? Even through it's a default cargo behavior.

nagisa added a commit to nagisa/cargo-fuzz that referenced this issue Mar 6, 2017
nagisa added a commit to nagisa/cargo-fuzz that referenced this issue Mar 6, 2017
@frewsxcv
Copy link
Member

You should be able to specify ASAN_OPTIONS="detect_leaks=0" now after the changes in #84

@frewsxcv
Copy link
Member

....or yeah, just pass it as flags to cargo fuzz run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants