Skip to content

fuzz: Limit toxic test globals to their respective scope #21849

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

Merged
merged 1 commit into from
May 4, 2021

Conversation

maflcko
Copy link
Member

@maflcko maflcko commented May 4, 2021

Globals in one fuzz target are toxic to all other fuzz targets, because we link all fuzz targets into one binary. Any code called by constructing the global will affect all other targets. This leads to incorrect coverage stats, false-positive crashes, ...

@fanquake fanquake added the Tests label May 4, 2021
@maflcko
Copy link
Member Author

maflcko commented May 4, 2021

No description provided.

@practicalswift
Copy link
Contributor

cr ACK cf83b82: non-toxic is better than toxic!

@laanwj
Copy link
Member

laanwj commented May 4, 2021

Code review ACK cf83b82

@maflcko maflcko merged commit 3f8f238 into bitcoin:master May 4, 2021
@maflcko maflcko deleted the 2105-fuzzToxic branch May 4, 2021 15:23
sidhujag pushed a commit to syscoin/syscoin that referenced this pull request May 5, 2021
…ve scope

cf83b82 fuzz: Limit toxic test globals to their respective scope (MarcoFalke)

Pull request description:

  Globals in one fuzz target are toxic to all other fuzz targets, because we link all fuzz targets into one binary. Any code called by constructing the global will affect all other targets. This leads to incorrect coverage stats, false-positive crashes, ...

ACKs for top commit:
  practicalswift:
    cr ACK cf83b82: non-toxic is better than toxic!
  laanwj:
    Code review ACK cf83b82

Tree-SHA512: 5b3a37bcb36fce4160c94f877b2c07704527e3e1842092375c793d2eca77b996ae62889326094020855666bb34fa019fcfe92e8ff8430ce0372227f03ab2b907
gwillen pushed a commit to ElementsProject/elements that referenced this pull request Jun 1, 2022
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Aug 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants