| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We want to be in the same global state each time we come in
FuzzerTestOneInput(). There are various reasons why we might not be that
include:
- Initialization that happens on first use. This is mostly the
RUN_ONCE() things, or loading of error strings.
- Results that get cached. For instance a stack that is sorted, RSA
blinding that has been set up, ...
So I try to trigger as much as possible in FuzzerInitialize(), and for
things I didn't find out how to trigger this it needs to happen in
FuzzerTestOneInput().
Reviewed-by: Rich Salz <rsalz@openssl.org>
GH: #2023
|
| |
|
|
|
|
|
|
| |
This allows to free everything we allocated, so we can detect memory
leaks.
Reviewed-by: Rich Salz <rsalz@openssl.org>
GH: #2023
|
| |
|
|
|
| |
Reviewed-by: Rich Salz <rsalz@openssl.org>
GH: #2023
|
| |
|
|
|
|
| |
Reviewed-by: Rich Salz <rsalz@openssl.org>
GH: #1276
|
|
|
Reviewed-by: Rich Salz <rsalz@openssl.org>
GH: #1229
|
