| commit | d1c5a05b185d9f9d7a04399fe30fc2192b66f5e7 | [log] [tgz] |
|---|---|---|
| author | Frederick Mayle <fmayle@google.com> | Mon Dec 16 15:42:59 2024 -0800 |
| committer | Frederick Mayle <fmayle@google.com> | Tue Dec 17 13:14:30 2024 -0800 |
| tree | f1d6380cfd78f86c08f3d10df6d78ad17e6b096e | |
| parent | a0c4595a769c606de78d7e74da34f6acae63ce02 [diff] |
delete custom panic hooks For non-test binaries, the default hook calls android_set_abort_message, which causes the panic message to be included in the crashdump output, so these hooks were redundant. For test binaries, the story is more complicated. Android uses `-Z panic-abort-tests`, which installs a panic hook to detect if the test panic'd and communicates the reason to the test framework. If a test binary installs its own custom panic hook, it breaks that setup and so the test framework will think the test crashed in an unknown manner. It is possible to use a custom hook without breaking it, but probably not worth the complexity. Panic messages from tests will no longer go to logcat, but they will now be reported as part of the test results, e.g. in `atest`'s stderr and in the test results web UI. Test: atest rialto_test Change-Id: Ib53248c054f8d358835501814568cec8bedf5f03
Android Virtualization Framework (AVF) provides secure and private execution environments for executing code. AVF is ideal for security-oriented use cases that require stronger isolation assurances over those offered by Android’s app sandbox.
Visit our public doc site to learn more about what AVF is, what it is for, and how it is structured. This repository contains source code for userspace components of AVF.
If you want a quick start, see the getting started guideline and follow the steps there.
For in-depth explanations about individual topics and components, visit the following links.
AVF components:
AVF APIs:
How-Tos: