oss-fuzz/docs/debugging.md

## Debugging Build Scripts

While developing your build script, it may be useful to run bash within the
container:

```bash
$ python infra/helper.py shell $TARGET_NAME  # runs /bin/bash within container
$ compile                                   # run compilation manually
```

## Debugging Fuzzers with GDB

If you decide to debug a fuzzer with gdb (which is already installed in libfuzzer-runner image),
you will need to start a container in privileged mode:

```bash
docker run -ti --privileged -v /tmp/out:/out -t ossfuzz/libfuzzer-runner /out/some_fuzzer_name
```
Create debugging.md 2016-10-04 18:54:45 +00:00			`## Debugging Build Scripts`

			`While developing your build script, it may be useful to run bash within the`
			`container:`

			```bash
replacing library with target 2016-10-25 23:36:29 +00:00			`$ python infra/helper.py shell $TARGET_NAME # runs /bin/bash within container`
[infra] fixing build script location (/src/build.sh) Fixing the location of build.sh gets rid of ENTRYPOINT. Which opens a possibility to implement different commands like: ````bash docker run -ti expat compile docker run -ti expat run <fuzzer_name> <input_data> ```` and keep the knowledge of build script location. This is a breaking change. 2016-10-06 20:45:12 +00:00			`$ compile # run compilation manually`
Create debugging.md 2016-10-04 18:54:45 +00:00			```

Update debugging.md 2016-11-02 19:42:00 +00:00			`## Debugging Fuzzers with GDB`
Update debugging.md 2016-10-04 18:57:14 +00:00
			`If you decide to debug a fuzzer with gdb (which is already installed in libfuzzer-runner image),`
			`you will need to start a container in privileged mode:`

			```bash
			`docker run -ti --privileged -v /tmp/out:/out -t ossfuzz/libfuzzer-runner /out/some_fuzzer_name`
			```