mirror of https://github.com/google/oss-fuzz.git
Update fuzzer_environment.md
This commit is contained in:
parent
3d351a0883
commit
d4151c7364
|
@ -2,6 +2,17 @@
|
|||
|
||||
Your fuzz targets will be run on a [Google Compute Engine](https://cloud.google.com/compute/) VM (Linux) with some security restrictions.
|
||||
|
||||
## Dependencies
|
||||
|
||||
You should not make any assumptions on the availability of dependent packages
|
||||
and libraries in the execution environment. Make sure to statically link any
|
||||
library dependencies with your fuzz target executable during build time
|
||||
([example](https://github.com/google/oss-fuzz/blob/master/projects/tor/build.sh#L40)).
|
||||
All build artifacts needed during fuzz target execution should be inside `$OUT`
|
||||
directory, and other directories like `$WORK`, `$SRC`, etc will not be accessible.
|
||||
You can ensure that the fuzz target works correctly by using `run_fuzzer` command
|
||||
(see instructions [here](docs/new_project_guide.md#testing-locally)).
|
||||
|
||||
## Current working directory
|
||||
|
||||
You should not make any assumptions about the current working directory of your
|
||||
|
@ -11,7 +22,7 @@ directory where your fuzz target executable is located.
|
|||
## File system
|
||||
|
||||
Everything except `/tmp` is read-only, including the directory that your fuzz target
|
||||
executable lives in. Note that `/tmp` is limited in size (64MB).
|
||||
executable lives in.
|
||||
|
||||
`/dev` is also unavailable.
|
||||
|
||||
|
|
Loading…
Reference in New Issue