| commit | 31acf26590b94384f950bee24680267a71380276 | [log] [tgz] |
|---|---|---|
| author | Jake Ehrlich <jakehehrlich@google.com> | Tue Jan 29 17:16:32 2019 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jan 30 02:16:25 2019 +0000 |
| tree | a93555da687fb5c30602544d6e377d5225b2f27a | |
| parent | 4e2ffa0e1d501359590c36c39ee3b7e5a6a8e4df [diff] |
[prebuilt] Roll symbolize
This adds support for using .build-id directories.
Bug: DX-209
Bug: TC-303
Test: 1) Symbolize some dummy markup against a release build
2) Symbolize result of crasher using symbolize script
3) Symbolize result of crasher using fx script
4) Symbolize result of crasher using the tool manually
to test .build-id stuff.
Change-Id: I26d4431e301a816ad18aa6d6410094ba06a3f313
Zircon is the core platform that powers the Fuchsia OS. Zircon is composed of a microkernel (source in kernel/...) as well as a small set of userspace services, drivers, and libraries (source in system/...) necessary for the system to boot, talk to hardware, load userspace processes and run them, etc. Fuchsia builds a much larger OS on top of this foundation.
The canonical Zircon Git repository is located at: https://fuchsia.googlesource.com/zircon
The Zircon Kernel provides syscalls to manage processes, threads, virtual memory, inter-process communication, waiting on object state changes, and locking (via futexes).
Currently there are some temporary syscalls that have been used for early bringup work, which will be going away in the future as the long term syscall API/ABI surface is finalized. The expectation is that there will be about 100 syscalls.
Zircon syscalls are generally non-blocking. The wait_one, wait_many port_wait and thread sleep being the notable exceptions.
This page is a non-comprehensive index of the zircon documentation.