| commit | 7317081f0a9224bcab432b3e7a8a1bb90c97f5ea | [log] [tgz] |
|---|---|---|
| author | Yifei Teng <yifeit@google.com> | Tue Dec 11 18:42:47 2018 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Dec 13 02:50:03 2018 +0000 |
| tree | 04f4eadd179c5f3ffda1759c727e62836be159c7 | |
| parent | 40c65901f414d83ab7f4bc1ead42abdf928ed7f1 [diff] |
[musl][crashsvc] Noisily fail when IO functions are not implemented in libc. Currently, if an app does not link in an implementation for POSIX IO functions e.g. read/write, they automatically fallback to a dummy implementation, which does nothing except silently fail. This change explores if it is better to just crash in those scenarios. The rationale is that in production, we should not be depending on these dummy implementations. And currently because of the build system, it is quite easy to forget to explicitly link in an implementation e.g. FDIO. After opting to explicitly crash, the following cases have been uncovered: 1. system/utest/util/listnode does not link FDIO. Hence it has no console output whatsoever. 2. system/core/crashsvc also does not link FDIO, but calls fprintf. Hence when we crash on unimplemented functions, it will forever recursively crash in the crash handler. This has also been fixed. TEST: Run all tests with the crashing behavior. And also try randomly removing FDIO from any test and verifies that it noisily crashes. Global Integration Test: integration/+/78875 Change-Id: I710e512068c2926f8ff09a2b71c806b7bf6f87df
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
A read-only mirror of the code is present at: https://github.com/fuchsia-mirror/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.