fuzzing: Add details about suppressing fuzzer errors.

Add details about how fuzzer errors can be suppressed using
sanitizer block list files.

TEST=Rendering in gitles looks ok.

Change-Id: I19028e1e302a87ee896fce6c0ee57fea5812a673
Reviewed-on: https://chromium-review.googlesource.com/1667872
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Commit-Ready: Manoj Gupta <manojgupta@chromium.org>
Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>
1 file changed
tree: a2e65aefe348d9c10b6e6da66cbb4dc33763e812
  3. PRESUBMIT.cfg
  4. README.md
  5. archive_mirrors.md
  6. ca_certs.md
  7. chrome_commit_pipeline.md
  8. contact.md
  9. containers_and_vms.md
  10. contributing.md
  11. cros_commit_pipeline.md
  12. cros_flash.md
  13. cros_vm.md
  14. dbus_best_practices.md
  15. dbus_in_chrome.md
  16. debug_buttons.md
  17. developer_guide.md
  18. development_basics.md
  19. eol_aue_process.md
  20. fuzzing.md
  21. glossary.md
  22. gsutil.md
  23. images/
  24. kernel_faq.md
  25. lsb-release.md
  26. navbar.md
  27. os_config.md
  28. packages/
  29. platform2_gn.md
  30. platform2_primer.md
  31. portage/
  32. reporting_bugs.md
  33. rust_on_cros.md
  34. sandboxing.md
  35. scripts/
  36. security/
  37. security_review_howto.md
  38. security_severity_guidelines.md
  39. security_sheriffing.md
  40. selinux.md
  41. simple_chrome_workflow.md
  42. source_layout.md
  43. unit_tests.md

Chromium OS docs

This directory contains public Chromium OS project documentation that is automatically rendered by Gitiles. The docs are written in Gitiles-flavored Markdown.

General guidelines

See the Chromium documentation guidelines and Chromium documentation best practices.

Style guide

Markdown documents must follow the style guide.

Making changes

This repository is managed by the repo tool, so you can make changes to it using the same techniques that you'd use for any other repositories in the project.

See the Contributing guide for more details.

Making changes without repo

You can also make changes to this repository without using the repo tool. This comes in handy when you don't have a Chromium OS checkout:

git clone https://chromium.googlesource.com/chromiumos/docs
curl -Lo .git/hooks/commit-msg https://gerrit-review.googlesource.com/tools/hooks/commit-msg
chmod +x .git/hooks/commit-msg
cd docs
git checkout -b changes
(make some changes)
git commit -a
git push origin HEAD:refs/for/master

The above steps will upload a patch to chromium-review.googlesource.com where you can get your patch reviewed, and submit.

Previewing changes

You can preview your local changes using scripts/preview_docs which utilizes Gerrit sandbox branches:

scripts/preview_docs README.md

You can also use md_browser, which is entirely local and does not require refs/sandbox/ push permission, but has somewhat inaccurate rendering:

# at top of Chromium OS checkout
./src/chromium/src/tools/md_browser/md_browser.py -d docs

Then browse to e.g. http://localhost:8080/README.md.

To review someone else's changes, apply them locally first, or just click the gitiles link near the top of a Gerrit file diff page.