Brad Fitzpatrick d36f4a5f13 StrictMode: gather and return violating stacks in Binder replies ... Now, when Thread A has a strict mode policy in effect and does a Binder call to Thread B (most likely in another process), the strict mode policy is passed along, but with the GATHER penalty bit set which overrides other policies and instead gathers all offending stack traces to a threadlocal which are then written back in the Parcel's reply header. Change-Id: I7d4497032a0609b37b1a2a15855f5c929ba0584d		2010-07-15 13:18:05 -07:00
..
Android.mk
Binder.cpp
BpBinder.cpp
IInterface.cpp
IMemory.cpp
IPCThreadState.cpp	More StrictMode work, keeping Binder & BlockGuard's thread-locals in-sync.	2010-07-15 13:18:05 -07:00
IPermissionController.cpp	Add Parcel::readExceptionCode() and Parcel::writeNoException()	2010-07-13 15:45:18 -07:00
IServiceManager.cpp	Add Parcel::readExceptionCode() and Parcel::writeNoException()	2010-07-13 15:45:18 -07:00
MemoryBase.cpp
MemoryDealer.cpp
MemoryHeapBase.cpp
MemoryHeapPmem.cpp
Parcel.cpp	StrictMode: gather and return violating stacks in Binder replies	2010-07-15 13:18:05 -07:00
Permission.cpp
ProcessState.cpp
Static.cpp