Merge "Fix stack trace logging in RefBase."
am dfdbb64f: Merge "Fix stack trace logging in RefBase."

* commit 'dfdbb64ff79df937e939f78ff70d5501f17e57d3':
  Fix stack trace logging in RefBase.
logd: build breakage in user

build breakage in branch: git_klp-dev-gpl @ 1101951

Change-Id: I4c9681bf4c97368ec19f5a79fef134aba937f337
Merge "logd: build breakage in user"
am 075828b8: Merge "logd: build breakage in user"

* commit '075828b83bd903465442dc5021004266d56e075c':
  logd: build breakage in user
Add CleanSpec for zygote changes.

default.prop is generated out of several makefile variables,
and it isn't possible to neatly express a dependency on those
variables (except perhaps by adding every possible makefile that
could define them to the deps list).

Change-Id: I93ea45c956aa22922f2389f735c058700621f674
Merge "Add CleanSpec for zygote changes."
am 223fc42b: Merge "Add CleanSpec for zygote changes."

* commit '223fc42b5e289e882f67c893374ffbef595a6901':
  Add CleanSpec for zygote changes.
logd: liblog: logcat: enable prune features for user

- Enable whitelist, blacklist and logsize tuneables for user

Change-Id: Id0c283844c71c5263a8cfbebf2e550f7ac415858
Handle errno properly to avoid corrupt str_parms

A normal sequence of calls is as follows:
str_parms_create_str, str_parms_add_str, str_parms_destroy.
In some cases the destroy caused double free.

str_parms_add_str will clone the input and send it to hashmapPut
for storage. If hashmapPut did not store the strings it will raise
errno = ENOMEM and leave caller with ownership of the strings.
In any of these cases it will be safe to destroy the str_parms.

But what if it wasn't hashmapPut that said NOMEM? What if there
was a stale NOMEM already before a successful hashmapPut?
In that case the strings will be successfully added to the list
(if new), but when str_parms_add_str sees the NOMEM it will free
them anyway, leaving dangling pointers in the str_parms!!

It is the responsibility of the caller to clear errno before any
interesting call. This patch makes sure that str_parms_add_str
reacts only on errno emmitted from hashmapPut.

Change-Id: If87e4bcc482f09e1c66133d33517b152ebdac65f
Merge "Handle errno properly to avoid corrupt str_parms"
am 5f130216: Merge "Handle errno properly to avoid corrupt str_parms"

* commit '5f130216762278331b5d97eaf1fb549680143c85':
  Handle errno properly to avoid corrupt str_parms
Create an UnwindMapLocal object.

The way libunwind handles local unwinds is different from remote unwinds,
so create a new map object to handle the differences.

Add new test to verify the map data is being generated correctly.

Add new tests to check for leaks.

Refactor the BACK_LOGW code into a single header file.

Change-Id: I01f3cbfc4b927646174ea1b614fa25d23b9b3427
Merge "Create an UnwindMapLocal object."
am a97798af: Merge "Create an UnwindMapLocal object."

* commit 'a97798afc9105668a80b775516a7cc4db341a62e':
  Create an UnwindMapLocal object.
logd: transitory reader thread create should be detached

Bug: 13692914
Change-Id: Ia7306e6e844ae9f17c6f594bf6b25f3148652570
Merge "logd: transitory reader thread create should be detached"
am d1d2c15d: Merge "logd: transitory reader thread create should be detached"

* commit 'd1d2c15de8ea09989e8072d197c22020860f1461':
  logd: transitory reader thread create should be detached
logd: Add pidToName helper

Change-Id: Idd8e804ab65feb8dc432150ae701464de1ad5302
logd: Add pidToUid helper

Change-Id: I23ebae1957c027bff6cbc2573a227bf0c44c08a2