Clean up abort.

* A dlmalloc usage error shouldn't call abort(3) because we want to
  cause a SIGSEGV by writing the address dlmalloc didn't like to an
  address the kernel won't like, so that debuggerd will dump the
  memory around the address that upset dlmalloc.

* Switch to the simpler FreeBSD/NetBSD style of registering stdio
  cleanup. Hopefully this will let us simplify more of the stdio
  implementation.

* Clear the stdio cleanup handler before we abort because of a dlmalloc
  corruption error. This fixes the reported bug, where we'd hang inside
  dlmalloc because the stdio cleanup reentered dlmalloc.

Bug: 9301265
Change-Id: Ief31b389455d6876e5a68f0f5429567d37277dbc

Conflicts:

	libc/bionic/libc_logging.cpp
	libc/stdio/findfp.c
	libc/stdio/local.h
	libc/upstream-freebsd/lib/libc/stdio/makebuf.c
	libc/upstream-freebsd/lib/libc/stdio/setvbuf.c
reconcile upstream-freebsd and pthread stuff with android-4.4_r1

Change-Id: I10a4d07395ab74d5dddc732d675f55d18c077c3c
Fix fortification inclusion

Change-Id: Ibd594305c865312a551775fa9a9a7bd5d05afc22
Werror is for suckas. We're from the streets

Change-Id: Ib45a94dfa8e34b9bb574026f1a97cf36fce52583
Try not building THIS, bionic.

Change-Id: Ib1863cb72c4e5a6589ff9a44fcb2f4c6e9dbaa23
Remove __strchr_chk.cpp NOT __strcat_chk.cpp

Change-Id: I6ecd8bbffc3f6051c3c650d878adffb55a9e730e
Get 4.4 building

Change-Id: Ie9007fc2f29b0c6b6984244a8484584528998da3