【问题标题】:JNI CallVoidMethod leads to Fatal signal 6 and invalid indirect referenceJNI CallVoidMethod 导致致命信号 6 和无效的间接引用
【发布时间】:2015-05-11 18:31:12
【问题描述】:

我正在尝试从 android-ndk 中发送短信。当我尝试在SmsManager 中调用sendTextMessage 方法时,我的应用程序崩溃,错误代码为6(中止)。此外,我收到一条错误消息,提示“decodeIndirectRef 中的间接引用 0xe7f03658 无效”。我认为这与我的对象引用有关,但据我所知,我正在使用的对象并未使用所述地址。

应用程序在执行最后一行时崩溃。我检查了所有异常情况,但没有出现异常情况。

#ifndef NULL
#define NULL   ((void *) 0)
#endif

#include <string.h>
#include <jni.h>
#include <android/log.h>

JNIEXPORT void JNICALL Java_tss_challenges_hybrid_App_sendSMS(JNIEnv* env,
        jobject thiz) {
    jclass smsManagerClz = (*env)->FindClass(env,
            "android/telephony/SmsManager");
    jmethodID getDefaultMethodID = (*env)->GetStaticMethodID(env, smsManagerClz,
            "getDefault", "()Landroid/telephony/SmsManager;");
    jobject smsManagerObj = (*env)->CallStaticObjectMethod(env, smsManagerClz,
            getDefaultMethodID);
    jmethodID sendSMSMethodID = (*env)->GetMethodID(env, smsManagerClz,
            "sendTextMessage",
            "(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;"
                    "Landroid/app/PendingIntent;Landroid/app/PendingIntent;)V");

    jstring number = (*env)->NewStringUTF(env, "1234");
    jstring text = (*env)->NewStringUTF(env, "sms content");
    jstring nullString = (*env)->NewStringUTF(env, NULL);

    __android_log_print(ANDROID_LOG_VERBOSE, "MyApp", "%x,%x,%x,%x,%x,%x,%x,%x", number, text, nullString,smsManagerObj,sendSMSMethodID,env,smsManagerClz,getDefaultMethodID);
    (*env)->CallVoidMethod(env, smsManagerObj, sendSMSMethodID, number, nullString, text, NULL, NULL);
}

日志:

05-11 14:17:00.718: D/dalvikvm(2376): Trying to load lib /data/app-lib/tss.chalenges.hybrid-1/libnativeSMSManager.so 0xb2d5b2d0
05-11 14:17:00.718: D/dalvikvm(2376): Added shared lib /data/app-lib/tss.chalenges.hybrid-1/libnativeSMSManager.so 0xb2d5b2d0
05-11 14:17:00.718: D/dalvikvm(2376): No JNI_OnLoad found in /data/app-lib/tss.chalenges.hybrid-1/libnativeSMSManager.so 0xb2d5b2d0, skipping init
05-11 14:17:00.848: V/MyApp(2376): c2900025,a0f00029,0,ba100021,b0be31c0,b82cff30,b680001d,b0be2f18
05-11 14:17:00.948: W/dalvikvm(2376): Invalid indirect reference 0xe7f03658 in decodeIndirectRef
05-11 14:17:00.948: I/dalvikvm(2376): "main" prio=5 tid=1 RUNNABLE
05-11 14:17:00.948: I/dalvikvm(2376):   | group="main" sCount=0 dsCount=0 obj=0xb2a94ca8 self=0xb82d3398
05-11 14:17:00.958: I/dalvikvm(2376):   | sysTid=2376 nice=0 sched=0/0 cgrp=apps handle=-1225264812
05-11 14:17:00.958: I/dalvikvm(2376):   | state=R schedstat=( 100000000 380000000 94 ) utm=6 stm=4 core=0
05-11 14:17:00.958: I/dalvikvm(2376):   at tss.challenges.hybrid.App.sendSMS(Native Method)
05-11 14:17:00.958: I/dalvikvm(2376):   at tss.challenges.hybrid.App.onCreate(App.java:36)
05-11 14:17:00.958: I/dalvikvm(2376):   at android.app.Activity.performCreate(Activity.java:5231)
05-11 14:17:00.958: I/dalvikvm(2376):   at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087)
05-11 14:17:00.958: I/dalvikvm(2376):   at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2159)
05-11 14:17:00.958: I/dalvikvm(2376):   at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2245)
05-11 14:17:00.958: I/dalvikvm(2376):   at android.app.ActivityThread.access$800(ActivityThread.java:135)
05-11 14:17:00.958: I/dalvikvm(2376):   at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1196)
05-11 14:17:00.958: I/dalvikvm(2376):   at android.os.Handler.dispatchMessage(Handler.java:102)
05-11 14:17:00.958: I/dalvikvm(2376):   at android.os.Looper.loop(Looper.java:136)
05-11 14:17:00.958: I/dalvikvm(2376):   at android.app.ActivityThread.main(ActivityThread.java:5017)
05-11 14:17:00.958: I/dalvikvm(2376):   at java.lang.reflect.Method.invokeNative(Native Method)
05-11 14:17:00.958: I/dalvikvm(2376):   at java.lang.reflect.Method.invoke(Method.java:515)
05-11 14:17:00.958: I/dalvikvm(2376):   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
05-11 14:17:00.958: I/dalvikvm(2376):   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
05-11 14:17:00.958: I/dalvikvm(2376):   at dalvik.system.NativeStart.main(Native Method)
05-11 14:17:00.998: E/dalvikvm(2376): VM aborting
05-11 14:17:01.018: A/libc(2376): Fatal signal 6 (SIGABRT) at 0x00000948 (code=-6), thread 2376 (halenges.hybrid)

【问题讨论】:

  • 关于帖子的标签,这是编译为C还是C++代码?看到我如何看不到您的函数被声明为extern "C",并且JNIEnv 的类型因__cplusplus 是否定义而不同(请参阅jni.h),我不确定您当前的env-&gt;... 调用在C++。
  • 我将标签更改为 C。我很确定它被编译为纯 C 代码。包含代码的文件是“.c”文件。我可以从其他地方获得这些信息吗?
  • 你能显示本机堆栈崩溃跟踪吗?应遵循“致命信号6”。如果您打开 CheckJNI (developer.android.com/training/articles/…),您应该会获得更详细的信息。

标签: android c android-ndk java-native-interface


【解决方案1】:

你不需要传递NULL STRING,你可以直接在那个参数的地方传递NULL

避免这种情况

jstring nullString = (*env)->NewStringUTF(env, NULL);

尝试使用NULL

jstring nullString = (*env)->NewStringUTF(env, "");

【讨论】:

  • 我过去只提供 NULL。但后来我发现了这个:stackoverflow.com/questions/11055609/… 并相应地更改了我的代码。这两个版本都会导致上述问题。我绝对想将 NULL 传递给函数。 jstring nullString = (*env)->NewStringUTF(env, "");是空字符串,不是吗?
猜你喜欢
  • 1970-01-01
  • 2016-01-05
  • 1970-01-01
  • 2014-04-29
  • 2014-12-21
  • 1970-01-01
  • 2012-05-26
  • 1970-01-01
  • 1970-01-01
相关资源
最近更新 更多