• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..15-Nov-2021-

test/H07-May-2022-

BUILD.gnH A D15-Nov-2021361 2215

README.mdH A D15-Nov-20211.3 KiB168

fuzzilli.statusH A D15-Nov-2021168 64

libreprl.cH A D15-Nov-202115.3 KiB481350

libreprl.hH A D15-Nov-20214.9 KiB11824

main.ccH A D15-Nov-20211.9 KiB7149

testcfg.pyH A D15-Nov-20211.2 KiB5936

README.md

1# Communication model of fuzzilli with V8
2
3## Source code
4
5On a low level, Fuzzilli communicates with v8 through the REPRL protocol, implemented on the fuzzer side by the libreprl C library in `Sources/libreprl/`. The main way of using the library is through the following three functions:
6
7`reprl_create_context()` this creates a new, empty REPRL context to be used by the following APIs.
8
9`reprl_initialize_context(ctx, argv, envp)` this initializes the given context and sets the argv and envp vectors to use for the child processes.
10
11`reprl_execute(ctx, code)` this executes the given code and returns the exit status. If necessary, a new child process is created for this. This involves creating pipes, forking itself, then setting filedescriptors, and using `execve` to execute the d8 binary. A child process can be reused for multiple executions, thus increasing fuzzing performance as the overhead of fork and execve are removed.
12
13## Coverage
14
15Coverage information are being monitored through shared memory. On the side of v8 it is monitored through SanitizerCoverage module of Clang compiler ( https://clang.llvm.org/docs/SanitizerCoverage.html ) Through shared memory information about edges are shared with fuzzilli which implements counter for error and covered branches of the V8 code in Sources/libcoverage/coverage.c
16