|author||Jocelyn Dang <firstname.lastname@example.org>||Thu Jun 01 10:28:52 2017 -0700|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Mon Jul 17 22:01:10 2017 +0000|
[unittest] Run an exception handler thread so crashes don't bubble up to system handler. To enable the exception handler, a test should be run with RUN_TEST_ENABLE_CRASH_HANDLER. Tests can then call REGISTER_CRASH to register any processes that are expected to crash. If a crash was registered and occurs, the exception is caught and the test resumes. If a crash was not registered, the exception will be passed up to crashlogger and then the test will fail immediately. At the conclusion of the test, if a crash was registered and did not occur, the test will fail. MG-802 Change-Id: Ie1a7dd3db33109e4c5ea9cfef75097df0365b35b
Magenta is the core platform that powers the Fuchsia OS. Magenta 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 Magenta Git repository is located at: https://fuchsia.googlesource.com/magenta
A read-only mirror of the code is present at: https://github.com/fuchsia-mirror/magenta
The Magenta 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 10s, not 100s of syscalls.
Magenta syscalls are generally non-blocking. The wait (one, many, set) family of syscalls, ioport reads, and thread sleep being the notable exceptions.
This page is a non-comprehensive index of the magenta documentation.