-
Notifications
You must be signed in to change notification settings - Fork 116
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
Comments
Cargo fuzz run target -- flags
…On Mar 6, 2017 4:20 PM, "Evgeniy Reizner" ***@***.***> wrote:
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).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#73>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AApc0tJio_EAlr66VS0RNNpIEQU1F868ks5rjBZIgaJpZM4MUNNd>
.
|
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
You should be able to specify |
....or yeah, just pass it as flags to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm getting:
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).
The text was updated successfully, but these errors were encountered: