A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0xb422105c50 in tid 2334 (FinalizerDaemon), pid 2302 (om.test.gpstest)
用adb logcat >crash.txt 抓出log后，找到crash日志，但是看不明白啊
--------- beginning of crash
05-22 15:02:39.816 21853 21862 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0xb422105c50 in tid 21862 (FinalizerDaemon), pid 21853 (om.test.gpstest)
05-22 15:02:39.913 22814 22814 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-22 15:02:39.913 22814 22814 F DEBUG : Build fingerprint: 'vivo/PD1610/PD1610:8.1.0/OPM1.171019.026/compil08022122:user/release-keys'
05-22 15:02:39.913 22814 22814 F DEBUG : Revision: '0'
05-22 15:02:39.913 22814 22814 F DEBUG : ABI: 'arm64'
05-22 15:02:39.913 22814 22814 F DEBUG : pid: 21853, tid: 21862, name: FinalizerDaemon >>> com.test.gpstest <<<
05-22 15:02:39.913 22814 22814 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xb422105c50
05-22 15:02:39.914 22814 22814 F DEBUG : x0 000000b422105c30 x1 0000007bc5408f30 x2 0012492492492493 x3 0000000000005400
05-22 15:02:39.914 22814 22814 F DEBUG : x4 0000000000000007 x5 01c0000000000000 x6 00000000ffffffff x7 0000000000000007
05-22 15:02:39.914 22814 22814 F DEBUG : x8 0000007c620fbe30 x9 000000000000007b x10 000000000000007c x11 0000000000000018
05-22 15:02:39.914 22814 22814 F DEBUG : x12 0000000000000003 x13 0000000000000001 x14 0000000000000000 x15 0000000001000000
05-22 15:02:39.914 22814 22814 F DEBUG : x16 0000007bc4403a28 x17 0000007bc5408f48 x18 0000000000000018 x19 0000007bdf000140
05-22 15:02:39.914 22814 22814 F DEBUG : x20 0000007bdeffd008 x21 0000007bc5408f48 x22 0000007bc5400000 x23 0000010e3701a980
05-22 15:02:39.914 22814 22814 F DEBUG : x24 0000000000165400 x25 0000010e3701a000 x26 00000000df000278 x27 0000007c620fc000
05-22 15:02:39.914 22814 22814 F DEBUG : x28 0000007c620fc000 x29 0000007bd05fe8e0 x30 0000007c620c04d4
05-22 15:02:39.914 22814 22814 F DEBUG : sp 0000007bd05fe880 pc 0000007c62099cb4 pstate 0000000080000000
05-22 15:02:40.031 1174 1949 D DisplayPowerController: mVivoWaitingBrightness brightness change from 142 to 179 delay 10
05-22 15:02:40.032 1174 1949 D DisplayPowerController: onNewScreenValue info:brightness=179;lightlevel=0;cameralevel=3;screenlevel=1;lightlux=2846;delaytime=10;reason=-1;version=1;date=unknown;proximity=false;
05-22 15:02:40.042 1174 1952 D DisplayPowerController: ddd vivoUpdateAutoBrightness brightnessBeenApplied=0
05-22 15:02:40.042 1174 1952 D DisplayPowerController: ALS update mScreenAutoBrightness from 142 to 179
05-22 15:02:40.042 1174 1952 D DisplayPowerController: vivoUpdateAutoBrightness mAutobrightInfo:brightness=179;lightlevel=0;cameralevel=3;screenlevel=1;lightlux=2846;delaytime=10;reason=-1;version=1;date=unknown;proximity=false;
05-22 15:02:40.043 1174 1332 D DisplayPowerController: updatePowerState: mPowerRequest.useProximitySensor=false, mProximity=Unknown, mScreenOffBecauseOfProximity=false mPowerRequest.screenState = ON mWaitingForNegativeProximity = false
05-22 15:02:40.043 1174 1332 D DisplayPowerController: animateScreenStateChange to target ON
05-22 15:02:40.043 1174 1949 E RgbBrightnessCurveAlgo: vivo_adjust_bar mChangeUpLux 3426 mChangeDownLux 1349 x_gm 2846 current_brightness 179
05-22 15:02:40.043 1174 1332 D DisplayPowerController: animateScreenStateChange to target ON
05-22 15:02:40.043 1174 1332 D DisplayPowerController: animateScreenStateChange after setScreenState
05-22 15:02:40.043 1174 1332 D DisplayPowerController: animateScreenStateChange after setScreenState
05-22 15:02:40.044 1174 1332 D DisplayPowerController: updatePowerState use=true enabled=true state=ON
05-22 15:02:40.045 1174 1332 I SettingsProvider: insert settings success:true, table:1 name:vivo_screen_auto_brightness value:179 pkg:android
05-22 15:02:40.054 1174 1956 D DisplayPowerState: Updating screen state: state=ON, backlight=143, backlightChanged= true mPowerAssistantMode= 0
05-22 15:02:40.055 1174 1956 I DisplayPowerState: mBlockedByFingerprint = 0
05-22 15:02:40.055 1174 1956 E DisplayPowerState: run changed=true mNightPearlManager is null! or state != Display.STATE_OFF
05-22 15:02:40.055 1174 1956 D DisplayPowerState: run normal set state ON brightness:143
uj5u.com熱心網友回復：
在logcat里只能看到這么一行，A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0xb422105c50 in tid 2334 (FinalizerDaemon), pid 2302 (om.test.gpstest)
而且捕獲不到，用UncaughtExceptionHandler也無法捕獲。
uj5u.com熱心網友回復：
換了個手機沒有出現這個問題，莫名奇妙，繼續等待高手。。。uj5u.com熱心網友回復：
偷偷告訴你，我之前用U3d的SDK也遇到這個問題，當時的技術支持回復我，說是so庫的問題，我猜測是cpu平臺的問題uj5u.com熱心網友回復：
解決了嗎！！！！！uj5u.com熱心網友回復：
還沒有 沒有哦轉載請註明出處，本文鏈接：https://www.uj5u.com/yidong/30523.html
標籤：Android
下一篇：Fortran 多執行緒問題