我们正在使用以下配置：
答案-1.4.6.aar，beta-1.2.10.aar，crashlytics-2.10.1.aar，crashlytics-core-2.6.7.aar，crashlytics-ndk，2.1.0.aar，fabric-1.4.7.aar
得到这个anr日志：
“crashlytics exception handler1”tid=32 waiting“crashlytics exception handler1”prio=5 tid=32 waiting | group=“main”scont=1 dscount=0 flags=1 obj=0x14242468 self=0x787b380800 | systid=11718 nice=10 cgrp=default sched=0/0 handle=0x78689c64f0 | state=s schedstat=（84559469 206904789 417）utm=4 stm=4 core=1 hz=100 |stack=0x78688c3000-0x78688c5000 stacksize=1041kb |保持互斥=
在java.lang.thread.parkfor$（线程）等待<0x022a44fe>（java.lang.object）的java.lang.object.wait（本机方法）。java:2137)在sun.misc.unsafe.park（不安全）处锁定<0x022a44fe>（java.lang.object）。java:358)在java.util.concurrent.locks.locksupport.park（locksupport。java:190)在java.util.concurrent.locks.abstractqueuedsynchronizer$conditionobject.await（abstractqueuedsynchronizer。java:2059)在java.util.concurrent.linkedblockingqueue.take（linkedblockingqueue。java:442)位于java.util.concurrent.threadpoolexecutor.gettask（threadpoolexecutor。java:1092)位于java.util.concurrent.threadpoolexecutor.runworker（线程池执行器。java:1152)在java.util.concurrent.threadpoolexecutor$worker.run（threadpoolexecutor。java:641)在io.fabric.sdk.android.services.common.executorutils$1$1.onrun（executorutils。java:75)在io.fabric.sdk.android.services.common.g.run（backgroundpriorityrunname。java:30)在java.lang.thread.run（线程。java:764)