Note that there are some explanatory texts on larger screens.

plurals
  1. POCan't debug native c++ code for Android in Eclipse on Windows
    primarykey
    data
    text
    <p>Does anyone know how to debug a Native Android Application from Eclipse on Windows? It looks like Linux users don't experience any problems with it.</p> <p>The main goal is to start debug process from Eclipse (without any console manipulations after each run).</p> <p>I went through a lot of tutorials but none of them made me able to break execution on set breakpoints in c++ code (I tried at least 10 of them). </p> <p>I have no CR LF problem in gdb.setup, I have C++ code compiled with <code>ndk-build -j8 NDK_DEBUG=1</code> Eclipse. All my breakpoints are set as a reaction on user click, so gdb should be already connected. When I click "Debug As Native Android Application", I get the following output:</p> <pre> warning: Could not load shared library symbols for 72 libraries, e.g. /system/bin/linker. Use the "info sharedlibrary" command to see the complete listing. Do you need "set solib-search-path" or "set sysroot"? warning: Unable to find dynamic linker breakpoint function. GDB will retry eventurally. Meanwhile, it is likely that GDB is unable to debug shared library initializers or resolve pending breakpoints after dlopen(). [New Thread 3239] [New Thread 3241] [New Thread 3242] [New Thread 3243] [New Thread 3244] [New Thread 3245] [New Thread 3246] [New Thread 3247] [New Thread 3248] The target endianness is set automatically (currently little endian) No symbol table is loaded. Use the "file" command. No symbol table is loaded. Use the "file" command. </pre> <p>Any ideas on what the problem is?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload