googleprojectzero / googleprojectzero/fuzzilli
ran into gn issue `No value named "exec_script_whitelist" in scope "build_dotfile_settings"` building fuzzilli in Docker
Open
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.3k
- Forks
- 367
- Avg merge
- 23h 53m
- Merged PRs (30d)
- 1
Description
Hello I was following https://github.com/googleprojectzero/fuzzilli/tree/main/Cloud/Docker
$ sudo ./build.sh v8
=> ERROR [18/18] RUN ./fuzzbuild.sh 0.6s
------
> [18/18] RUN ./fuzzbuild.sh:
0.440 ERROR at //.gn:36:48: No value named "exec_script_whitelist" in scope "build_dotfile_settings"
0.440 exec_script_whitelist = build_dotfile_settings.exec_script_whitelist +
0.440 ^--------------------
0.561 ninja: Entering directory `./out/fuzzbuild'
0.562 ninja: fatal: chdir to './out/fuzzbuild' - No such file or directory
------
Dockerfile:42
--------------------
40 | # Start building!
41 | ADD fuzzbuild.sh fuzzbuild.sh
42 | >>> RUN ./fuzzbuild.sh
43 |
--------------------
ERROR: failed to build: failed to solve: process "/bin/sh -c ./fuzzbuild.sh" did not complete successfully: exit code: 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Cloud/Docker instructions, then inspect Dockerfile at line 42 and fuzzbuild.sh. Reproduce with sudo ./build.sh v8 and read .gn around line 36, where build_dotfile_settings.exec_script_whitelist fails. Done means the Docker build completes and creates ./out/fuzzbuild successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, swift
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100