tree b7b61d2b2bf37a394026e19dad3ecacd08681fef
parent 3e829060cf3f604a0cd164759b5635ea480828bc
author Yi Kong <yikong@google.com> 1566719162 -0700
committer Yi Kong <yikong@google.com> 1566781544 +0000

Workaround ASAN false positive

There is a known ASAN false positive case. If a part of the application
is built with asan and another part is not instrumented, and both parts
use e.g. instrumented std::vector, asan may report non-existent
container overflow. This happens because instrumented and
non-instrumented bits of std::vector, inlined and not, are mixed during
linking, so you end up with incompletely instrumented std::vector.

https://github.com/google/sanitizers/wiki/AddressSanitizerContainerOverflow

Workaround the issue by statically linking in libbase, thus its code also
becomes instrumented.

Test: Run resolv_integration_test
Bug: 139838864
Bug: 131328001
Change-Id: I9fe0fcb57016273e505810345162ce6c55565381
Exempt-From-Owner-Approval: Fix build breakage, no functionality change.