| commit | 40f0c5cad3c32aff1080e8e401a554898967598d | [log] [tgz] |
|---|---|---|
| author | Elliott Hughes <enh@google.com> | Fri Oct 06 22:34:36 2023 +0000 |
| committer | Elliott Hughes <enh@google.com> | Fri Oct 06 22:34:36 2023 +0000 |
| tree | a833c0404825e65716670895707e46d91580ba6a | |
| parent | b89b3f6108cbec5a38d0d93d28b55f3d3d34adab [diff] |
Have the sanitizers trap rather than abort. abort() seems friendlier, but in practice it puts a couple of irrelevant libc.so frames on the top of the stack trace and clobbers all the registers that might have helped remotely debug a sanitizer failure. Let's switch to trapping directly in the sanitized code instead. Bug: http://b/298741930 Test: treehugger Change-Id: I4fca63cb42bfba16a934c1fa88b08697faf3be41
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.