android开发中使用dlclose出现软件崩

Question

本人用NDK-R7开发，发现在程序结尾使用dlclose会导致软件崩溃，有没有这方便懂得能指点下的

Answer 1

这通常都是memory使用上出现问题了， debug要看具体情况而定

Answer 2

06-19 14:00:49.095: I/DEBUG(1166): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-19 14:00:49.095: I/DEBUG(1166): Build fingerprint: 'Motorola/titanium/titanium/titanium:2.2.2/TITA_M2_17.19.0/1311656184:user/release-keys'
06-19 14:00:49.095: I/DEBUG(1166): pid: 2596, tid: 2682  >>> com.dingli.service.test <<<
06-19 14:00:49.095: I/DEBUG(1166): signal 11 (SIGSEGV), fault addr 81b0e58c
06-19 14:00:49.095: I/DEBUG(1166):  r0 00000000  r1 00000081  r2 00000001  r3 00000000
06-19 14:00:49.095: I/DEBUG(1166):  r4 00222b90  r5 00237d50  r6 811cc8c4  r7 00264f98
06-19 14:00:49.095: I/DEBUG(1166):  r8 00265558  r9 00237d64  10 48c3f000  fp 002379b8
06-19 14:00:49.095: I/DEBUG(1166):  ip 81206698  sp 48d3ee78  lr afd1058c  pc 81b0e58c  cpsr 60000030
06-19 14:00:49.095: I/DEBUG(1166):  d0  414000003f800000  d1  4100000000000000
06-19 14:00:49.095: I/DEBUG(1166):  d2  000000013f800000  d3  0000000000000000
06-19 14:00:49.095: I/DEBUG(1166):  d4  000000003f800000  d5  43f0000000000000
06-19 14:00:49.095: I/DEBUG(1166):  d6  00e01f0000000000  d7  416c03e010000000
06-19 14:00:49.095: I/DEBUG(1166):  d8  0000000000000000  d9  0000000000000000
06-19 14:00:49.095: I/DEBUG(1166):  d10 0000000000000000  d11 0000000000000000
06-19 14:00:49.095: I/DEBUG(1166):  d12 0000000000000000  d13 0000000000000000
06-19 14:00:49.103: I/DEBUG(1166):  d14 0000000000000000  d15 0000000000000000
06-19 14:00:49.103: I/DEBUG(1166):  scr 60000012
06-19 14:00:49.165: I/DEBUG(1166):          #00  pc 81b0e58c  
06-19 14:00:49.165: I/DEBUG(1166):          #01  pc 00010588  /system/lib/libc.so
06-19 14:00:49.165: I/DEBUG(1166): code around pc:
06-19 14:00:49.165: I/DEBUG(1166): 81b0e56c ffffffff ffffffff ffffffff ffffffff 
06-19 14:00:49.165: I/DEBUG(1166): 81b0e57c ffffffff ffffffff ffffffff ffffffff 
06-19 14:00:49.165: I/DEBUG(1166): 81b0e58c ffffffff ffffffff ffffffff ffffffff 
06-19 14:00:49.165: I/DEBUG(1166): 81b0e59c ffffffff ffffffff ffffffff ffffffff 
06-19 14:00:49.165: I/DEBUG(1166): 81b0e5ac ffffffff ffffffff ffffffff ffffffff 
06-19 14:00:49.165: I/DEBUG(1166): code around lr:
06-19 14:00:49.165: I/DEBUG(1166): afd1056c e3570002 1affffdf e3580000 e1a00006 
06-19 14:00:49.165: I/DEBUG(1166): afd1057c 13a01001 03a01081 e3a02001 ebfff97b 
06-19 14:00:49.165: I/DEBUG(1166): afd1058c e1a00005 e8bd87f0 00031e84 00001618 
06-19 14:00:49.165: I/DEBUG(1166): afd1059c e92d47f0 e2504000 e59f5174 03a00016 
06-19 14:00:49.165: I/DEBUG(1166): afd105ac e08f5005 08bd87f0 e5946000 e5948000 
06-19 14:00:49.165: I/DEBUG(1166): stack:
06-19 14:00:49.165: I/DEBUG(1166):     48d3ee38  afd43940  /system/lib/libc.so
06-19 14:00:49.165: I/DEBUG(1166):     48d3ee3c  afd0fd6c  /system/lib/libc.so
06-19 14:00:49.165: I/DEBUG(1166):     48d3ee40  00004000  
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee44  00000000  
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee48  00004000  
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee4c  00000002  
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee50  00222b90  [heap]
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee54  00237d50  [heap]
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee58  811cc8c4  
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee5c  00264f98  [heap]
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee60  00265558  [heap]
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee64  00237d64  [heap]
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee68  48c3f000  
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee6c  81202b13  /data/data/com.dingli.service.test/lib/libminiSDL.so
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee70  df002777  
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee74  e3a070ad  
06-19 14:00:49.173: I/DEBUG(1166): #01 48d3ee78  81b193e0  
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee7c  002a84a0  [heap]
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee80  81b193e0  
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee84  81b0f93b  
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee88  002662c8  [heap]
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee8c  00000000  
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee90  00264fa4  [heap]
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee94  002379c4  [heap]
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee98  00000000  
06-19 14:00:49.173: I/DEBUG(1166):     48d3ee9c  afd215bf  /system/lib/libc.so
06-19 14:00:49.173: I/DEBUG(1166):     48d3eea0  00000000  
06-19 14:00:49.181: I/DEBUG(1166):     48d3eea4  afd0fdcc  /system/lib/libc.so
06-19 14:00:49.181: I/DEBUG(1166):     48d3eea8  81204fec  /data/data/com.dingli.service.test/lib/libminiSDL.so
06-19 14:00:49.181: I/DEBUG(1166):     48d3eeac  00000001  
06-19 14:00:49.181: I/DEBUG(1166):     48d3eeb0  0000001f  
06-19 14:00:49.181: I/DEBUG(1166):     48d3eeb4  00100000  [heap]
06-19 14:00:49.181: I/DEBUG(1166):     48d3eeb8  81202ed9  /data/data/com.dingli.service.test/lib/libminiSDL.so
06-19 14:00:49.181: I/DEBUG(1166):     48d3eebc  002379b8  [heap]以上是eclipse中debug中出现的信息，自己打的log无法查找到原因

Answer 3

android下调试目前主流是不是看logcat中的信息，还有没有其他方法的

Answer 4

我的业务库用到libminiSDL.so，加入我把业务库dlclose掉了，libminiSDL.so会关闭吗