ERROR: AddressSanitizer: heap-buffer-overflow on address 0x615000000ffa
READ of size 2 at 0x615000000ffa thread T0
SCARINESS: 24 (2-byte-read-heap-buffer-overflow-far-from-bounds)
#0 0x885e06 in tt_face_vary_cvtsrc/truetype/ttgxvar.c:1556:31
Android, even if only the AOSP part, is probably a great candidate for the "eat your own dog food" exercise.
I remember using a tool called BoundsChecker on Windows 3.1 apps. It would intercept all API calls looking for issues, in particular looking for the proper freeing of Windows handles and memory. I wonder a similar principle could be applied to monitor how the low level libraries are used? The great thing about it was its ease of use.
The comments you read and contribute here belong only to the person who posted them. We reserve the right to remove off-topic comments.