2012-07-18 39 views
1

我需要更改文件名稱(/system/etc/asound.conf)在Android本機jni。 我可以運行shell CMD爲此在串口:我得到以下錯誤,同時執行外殼的機器人jni

mount -o remount rw /system 
busybox mv /system/etc/asound.conf /system/etc/asoundback.conf 
mount -o remount r /system 

首先,我在上面的shell腳本在Java中通過調用Runtime.getRuntiem(字符串)運行。 Ihis將導致所有的Android系統服務重新加載。所以我沒有這樣做。

我上面的shell腳本的JNI通過這樣調用系統()運行:

android_media_AudioSystem_changeFileName(JNIEnv *env, jobject thiz, jstring from, jstring to) 
{ 
    const jchar* c_from = env->GetStringCritical(from, 0); 
    String8 c_from8; 
    if (from) { 
     c_from8 = String8(c_from, env->GetStringLength(from)); 
     env->ReleaseStringCritical(from, c_from); 
    } 

    const jchar* c_to = env->GetStringCritical(to, 0); 
    String8 c_to8; 
    if (to) { 
     c_to8 = String8(c_to, env->GetStringLength(to)); 
     env->ReleaseStringCritical(to, c_to); 
    } 

    LOGV("*********** android_media_AudioSystem_changeFileName from: %s ,to: %s" ,c_from8 ,c_to8); 
    char buff[4096]; 
    sprintf(buff ,"mount -o remount rw /system;busybox mv %s %s;mount -o remount r /system" ,c_from8 ,c_to8); 
    if(system(buff) == -1) return -1; 
    return 0; 
} 

它不工作。日誌是:

[ 197.520000] mclkdiv = 2, bitclkdiv = 12 
D/ALSAModule(1160): open called for devices 00000002 in mode 0... 
E/ALSALib (1160): external/alsa-lib/src/pcm/pcm.c:2203:(snd_pcm_open_noupdate) Unknown PCM AndroidPlayback_Speaker_normal 
E/ALSALib (1160): external/alsa-lib/src/pcm/pcm.c:2203:(snd_pcm_open_noupdate) Unknown PCM AndroidPlayback_Speaker 
E/ALSALib (1160): external/alsa-lib/src/pcm/pcm.c:2203:(snd_pcm_open_noupdate) Unknown PCM AndroidPlayback 
I/ALSAModule(1160): Initialized ALSA PLAYBACK device defaul 
D/SoundSettings(2041): ******* audio channel: codec 
D/SoundSettings(2041): ******* before asound-----> asoundback 
I/AudioSystem(2041): *********** android_media_AudioSystem_changeFileName 
F/libc (2041): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1) 
I/DEBUG (1155): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 
I/DEBUG (1155): Build fingerprint: 'android:4.0.3/IML74K/eng.android.20120717.210618:eng/test-keys' 
I/DEBUG (1155): pid: 2041, tid: 2041 >>> com.android.settings <<< 
I/DEBUG (1155): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaadI/DEBUG (1155): r0 deadbaad r1 00000001 r2 40000000 r3 00000000 
I/DEBUG (1155): r4 00000000 r5 00000027 r6 62100021 r7 411afa18 
I/DEBUG (1155): r8 be9b8644 r9 be9b864c 10 4786445b fp be9b8684 
I/DEBUG (1155): ip ffffffff sp be9b8618 lr 40068f01 pc 40065660 cpsr 60000030 
I/DEBUG (1155):   #00 pc 00017660 /system/lib/libc.so 
I/DEBUG (1155):   #01 pc 0006f9de /system/lib/libandroid_runtime.so 
I/DEBUG (1155):   #02 pc 0001ebf0 /system/lib/libdvm.so (dvmPlatformInvoke) 
I/DEBUG (1155):   #03 pc 00058c38 /system/lib/libdvm.so (_Z16dvmCallJNIMethodPKjP6JValuePK6MethodP6Thread) 
I/DEBUG (1155): 
I/DEBUG (1155): code around pc: 
I/DEBUG (1155): 40065640 4623b15c 2c006824 e026d1fb b12368db \.#F$h.,..&..h#. 
I/DEBUG (1155): 40065650 21014a17 6011447a 48124798 24002527 .J.!zD.`.G.H'%.$ 
I/DEBUG (1155): 40065660 f7f47005 2106ef70 effef7f5 460aa901 .p..p..!.......F 
I/DEBUG (1155): 40065670 f04f2006 94015380 94029303 ebc8f7f5 . O..S.......... 
I/DEBUG (1155): 40065680 4622a905 f7f52002 f7f4ebd2 2106ef5c .."F. ......\..! 
I/DEBUG (1155): 
I/DEBUG (1155): code around lr: 
I/DEBUG (1155): 40068ee0 41f0e92d 46804c0c 447c2600 68a56824 -..A.L.F.&|D$h.h 
I/DEBUG (1155): 40068ef0 e0076867 300cf9b5 dd022b00 47c04628 gh.....0.+..(F.G 
I/DEBUG (1155): 40068f00 35544306 37fff117 6824d5f4 d1ee2c00 .CT5...7..$h.,.. 
I/DEBUG (1155): 40068f10 e8bd4630 bf0081f0 000285fa 41f0e92d 0F..........-..A 
I/DEBUG (1155): 40068f20 fb01b086 9004f602 461f4815 4615460c .........H.F.F.F 
I/DEBUG (1155): 
I/DEBUG (1155): memory map around addr deadbaad: 

Someelse可以幫我嗎?非常感謝!!!

回答

1

我不是在tracelogs的專家,但是從我可以利用它你:

1. Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1) 

這意味着內存損壞,deadbaad意味着損壞的內存..

2. I/DEBUG (1155): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaadI/DEBUG (1155): r0 deadbaad r1 00000001 r2 40000000 r3 00000000 

這是指註冊表爲空或0 ..

我不禁進一步,因爲我不知道你在做什麼,但我猜你是在錯誤地讀某處..

+0

你從哪裏得到0xdeadbaad這個含義是內存損壞的來源?好奇:) – t0mm13b 2012-07-18 20:11:54

+1

這裏是一個很不錯的解釋http://kobablog.wordpress.com/2011/05/14/how-to-read-crash-dump-of-android/ 它並不總是內存腐敗,但它是在大多數情況下... – Tancho 2012-07-18 20:30:58

+0

乾杯:)從我+1! – t0mm13b 2012-07-18 20:37:14