Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid: Eclipse gdb error when debugging native code
    primarykey
    data
    text
    <p>I followed a couple of tutorials on line, trying to setup gdb to debug native code:</p> <ol> <li>Chapter 11 of the book Android NDK Beginners Guide.</li> <li>Video: <a href="http://www.youtube.com/watch?v=hMV7Xqcn39k&amp;list=PLD89B891EF9D26F14&amp;feature=mh_lolz" rel="nofollow">http://www.youtube.com/watch?v=hMV7Xqcn39k&amp;list=PLD89B891EF9D26F14&amp;feature=mh_lolz</a></li> <li>Forum: <a href="http://wiki.eclipse.org/Sequoyah/ndk_guide" rel="nofollow">http://wiki.eclipse.org/Sequoyah/ndk_guide</a></li> </ol> <p>None of them got my debugger working completely.</p> <p>I now have a specific problem by following steps, which are agreed by all the above tutorials as the correct steps to debug native code:</p> <ol> <li>In Eclipse, Start my JAVA debugging session and stops at the first breakpoint in my onCreate() method.</li> <li>In terminal, under my project folder, run ndk-build-eclipse (the copy of the original ndk-gdb without the last line about auto-connecting gdb client to server), with no obvious warning or errors.</li> <li>In terminal, chmod +x MY_PROJECT/obj/local/armeabi/app_process (I'm on a mac), otherwise I'll get "Cannot run MY_PROJECT/obj/local/armeabi/app_process, for unknown reason" error. This app_process is set as GDB debugger in my C++ debug configuration.</li> <li>In Eclipse, start my C++ debug configuration.</li> </ol> <p>Then I got an error dialog say:</p> <pre><code>Error creating session Process Terminated Process Terminated Process Terminated </code></pre>
    singulars
    1. This table or related slice is empty.
    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