Fork from pix106's tree
startListeningBlocking is meant to be called under a reader thread, which is the case if startListeningNonBlocking calls it. A LocIpc client may delete the LocIpc obj, which would trigger sending an ABORT msg to the reader thread before it is subsequently deleted, in which case, it is possible that when the reader thread comes around to process the ABORT msg, referencing the data members of the possibly stale obj would cause unpredictable behaviors. Change-Id: I441af85c04d92b6fff695c020e3e0b4bd5e90409 CRs-Fixed: 2380093 |
||
---|---|---|
android | ||
build | ||
core | ||
etc | ||
gnss | ||
location | ||
pla | ||
utils | ||
Android.mk | ||
CleanSpec.mk | ||
configure.ac | ||
loc-hal.pc.in | ||
Makefile.am |