Ndk-gdb: "Character table not loaded"

Question

I'm still with ndk-gdb, now I'm trying to solve the main problem that made me complete another question, to which I myself answered xD

ndk-gdb tells me that there is no character table for my current library. This is similar to the file that I am debugging, where it does not match the file that the emulator launches. But I reloaded the application. It also says “use the file command”, but the file only when I debug the local program, right? This is not suitable when I debug remotely, like using Android.

So what should I do? I am looking for a solution from 3 days, but I still do not know. Maybe I should ask, what are the other reasons for this message besides the file problem?

Thanks. Some information: ndk-build and ndk-gdb, called in the proyect parent directory. android api level 10 (2.3.3) android ndk r7b

Android.mk file contents:

MY_LOCAL_PATH := $(call my-dir) LOCAL_PATH := $(MY_LOCAL_PATH) include $(CLEAR_VARS) LOCAL_MODULE := wrapper LOCAL_SRC_FILES := wrapper.c \ aes.c \ password.c \ sha256.c \ aescrypt.c include $(BUILD_SHARED_LIBRARY) 

Answer 1

If you are using Eclipse / Sequoyah, check the obj / local / armeabi / gdb2.setup file containing only the valid final Unix line style <0A>.

The generated file containing bad end lines <0D> <0D> <0A>, I received the message:

Character table is not loading. Use the file command.

Answer 2

 No symbol table is loaded. Use the "file" command. 

This message may occur if the directory path to the workspace has a space in the name, for example, "C: \ Documents and Settings \ myworkspace", the solution is to use a path without a space, for example, C: \ myworkspace "

Answer 3

I also encounter this problem as I try to debug the shared library before loading it, below is my process, although it is written in Chinese, you can use Google translate, good luck!

http://blog.csdn.net/xinfuqizao/article/details/7625886

Answer 4

Another problem that can lead to the loading of the "No Character Table" table is when the ndk-gdb script fails to pull out the app_process file from your phone.

This happened to me due to an error in ndk-gdb.py, where his code to check for the presence of "app_process32" mistakenly succeeded. Instead of returning to "app_process" as the script did, he tried to load a nonexistent file.