Deliberately leak our cached tag.

HWASan was unhappy that some binder code was calling `__android_log_print`
and accessing `last_tag` during exit, after liblog's destructors had
run. The old code didn't have this issue because it just leaked its
`char*`, so that seems like an easy fix.

Yet another case where we should have had -Wexit-time-destructors...
I'll come back for that rather than try to fix everything at once (since
this isn't the only one).

Bug: http://b/181830525
Test: treehugger
Change-Id: I0e5a57dc0b6479e757dd10dce7bb8ea74bd577c1
1 file changed
tree: 2db2cfdbb60e587b50eb38f26a6fd0f22dd0ad29
  1. liblog/
  2. logcat/
  3. logd/
  4. logwrapper/
  5. OWNERS
  6. PREUPLOAD.cfg
  7. TEST_MAPPING