1. I'm not aware of any. 2. A few things to try: - can you repeat the bug with same software running on another (released) device with different chipset? This would help show whether the bug is likely portable or specific to this device/chipset. - try a different kernel version - try disabling all but 1 cpu; if the problem goes away it may be related to SMP / missing barrier - worst case, write a low-level stress test just for this one issue
On Dec 29, 10:54 am, Shashank <[email protected]> wrote: > We are facing some random issues with futex while porting ICS on our > devices. > > Issue description: > --------------------- > > We are seeing random futex deadlock issues on ICS with different > processes on Android. > > One of the example is, we run a perl script that install/uninstall > multiple apks on device using adb. As install process adb daemon > (adbd) on the device forks another child process to handle this new > install request. In the failure case I saw that this new adbd child > process was sleeping in the futex queue, because of which adb request > on host was just waiting for reply back. This scenario is very random. > > In another case we saw dexpot getting stuck randomly during boot up > while running a malloc call. From stack trace it again turned out it > was sleeping in the futex queue (malloc -> dlmalloc -> futex). > > Questions: > -------------- > > 1) Has anyone seen such issue? > 2) How folks at Google generally debug pthead/futex code in libc > library under bionic? > > Thanks! > --Shashank -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
