Debugging Android JNI/C++ No Debug Symbols Found Target Machine Actively Refused Connection

爱⌒轻易说出口 提交于 2020-01-04 08:27:52

问题


Here is the console log:

(no debugging symbols found) D:\ws\test\MyProject\obj\local\armeabi\gdb2.setup:4: Error in sourced command file: :5039: No connection could be made because the target machine actively refused it. localhost:5039: No connection could be made because the target machine actively refused it.

Following debug steps for eclipse plugin sequoyah: http://www.eclipse.org/sequoyah/documentation/native_debug.php

I'm almost at the end trying to connect the C++ Debugging.

My Android.mk does have the following set:

LOCAL_CFLAGS := -g

this is the gdb I'm using ... I'm on windows.
C:\android-ndk-r7\toolchains\x86-4.4.3\prebuilt\windows\bin\i686-android-linux-gdb.exe

I'm still trying to get this to work for days. Could you provide someone (hopefully on Sequoyah team) provide some insight into how to get this to work on Windows.


回答1:


Did you run ndk-gdb from the terminal in the project directory? That fixed the problem for me




回答2:


You need to do adb forwarding before you can do that.

do adb forward tcp:5039 tcp:5039 and then try




回答3:


The instructions mention doing this to your gdb2.setup file:

removing the target remote:5039 statement

Did you remember to do that?



来源:https://stackoverflow.com/questions/8410639/debugging-android-jni-c-no-debug-symbols-found-target-machine-actively-refused

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!