| commit | d527172d4656e49e06449e4b859169743670c9d9 | [log] [tgz] |
|---|---|---|
| author | Harry Cutts <hcutts@chromium.org> | Mon Jan 10 23:41:42 2022 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu Jan 13 20:05:53 2022 |
| tree | 4421c5dbb7e9dddf97020729cfd5cc31aa2c1790 | |
| parent | 46e2b6e97f730bdd89b2a13e38064f42d8b100aa [diff] |
sandboxing: add section on finding failing syscalls I suspect this is a very common problem to have, so putting it in its own section should make it easier to find, compared to being mixed in to the variety of troubleshooting tips. I've also made some of the steps a bit more explicit, thanks to help from dverkamp@. BUG=none TEST=check gitiles rendering Change-Id: Ib2d3fd09a3b8c09ed12f27b8ae8178617affaf1a Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/docs/+/3379763 Reviewed-by: Mike Frysinger <vapier@chromium.org> Commit-Queue: Harry Cutts <hcutts@chromium.org> Tested-by: Harry Cutts <hcutts@chromium.org>
This directory contains public Chromium OS project documentation that is automatically rendered by Gitiles. The docs are written in Gitiles-flavored Markdown.
See the Chromium documentation guidelines and Chromium documentation best practices.
Markdown documents must follow the style guide.
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.
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 cd docs curl -Lo .git/hooks/commit-msg https://gerrit-review.googlesource.com/tools/hooks/commit-msg chmod +x .git/hooks/commit-msg git checkout -b changes (make some changes) git commit -a git push origin HEAD:refs/for/main
The above steps will upload a patch to chromium-review.googlesource.com where you can get your patch reviewed, and submit.
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.