How to Use Eclipse to Debug JNI code (Java & C/C++)

by

For those looking to debug NDK/JNI code in the Eclipse Juno release, it is essentially built into the software after installing the Android plugins and CDT plugins. You may have issues though since there is a problem that was introduced with the C/C++ Development tools (CDT 8.1) that as of 7/24/12 has not been fixed. For details on the issue see the following link. If you just want to debug, keep reading.

http://code.google.com/p/android/issues/detail?id=33788

If it is working correctly, you simply set your breakpoints in the C and Debug As -> Android Native Application. Unfortunately, you can not debug the java and C at the same time. If the problem is in the Java and you want to debug you do so by clicking Debug As -> Android Application.

If it is not working correctly, and you want to figure out how to get it correctly, the following packages worked for me.

  Android DDMS  20.0.1.v201207132230-403220
  Android Development Tools 20.0.1.v201207132230-403220 
  Android Hierarchy Viewer  20.0.1.v201207132230-403220 
  Android Native Development Tools  20.0.1.v201207132230-403220 
  Android Traceview 20.0.1.v201207132230-403220 
  Autotools support for CDT (Incubation)    3.0.1.201202152032  
  C/C++ Development Tools   8.0.2.201202111925  
  C/C++ Development Tools SDK   8.0.2.201202111925
  C/C++ Library API Documentation Hover Help (Incubation)   
  Eclipse SDK   4.2.0.I20120608-1400    
  Tracer for OpenGL ES  20.0.1.v201207132230-403220

The android packages came from setting Work With: option on the Eclipse Help->Install New Software… dialog to

dl-ssl.google.com/android/eclipse/

The older 8.02… CDT packages came from setting the Work With: option to the Indigo release packages.

download.eclipse.org/releases/indigo

If installed, you will need to remove the Android tools, and the new version of the CDT prior to installing the old version of the CDT. Once the 8.02… version of CDT is installed, you can install the Android tools and commence debugging.

Ensure you use the Build command “ndk-build NDK_DEBUG=1”

Autotools may not be required but since it is installed I have it listed.

Note that stepping through the code can be quirky sometimes.

More Related Contents:

  1. Failed to load the JNI shared Library (JDK)
  2. Eclipse java debugging: source not found
  3. Break when exception is thrown
  4. Calling a java method from c++ in Android
  5. JBoss debugging in Eclipse
  6. How to use conditional breakpoint in Eclipse?
  7. Eclipse – debugger doesn’t stop at breakpoint
  8. How to pass C structs back and forth to Java code in JNI?
  9. Locally declared variables can not be inspected
  10. Viewing complete strings while debugging in Eclipse
  11. How do I deal with a ClassNotLoadedException while debugging?
  12. Eclipse logcat debugging
  13. Eclipse debugging “source not found”
  14. Java object ID in jvm
  15. Eclipse reported “Failed to load JNI shared library” [duplicate]
  16. Error “A JNI error has occurred. Please check your installation and try again in Eclipse x86 Windows 8.1”
  17. How to find out if “debug mode” is enabled
  18. Determine if a java application is in debug mode in Eclipse
  19. Can I find out the return value before returning while debugging in Eclipse?
  20. Debugging Android NDK C/C++ code in Eclipse – breakpoints are not hit
  21. Running a program in Debug mode is incredible slow
  22. How to detect when a variable changes value
  23. Where do you configure Eclipse Java compiler (javac) flags?
  24. Breakpoint at exception in Eclipse – how to examine Exception object?
  25. Best way to debug Java web application packaged as a WAR using Eclipse and Maven?
  26. Why does the Eclipse debugger give the error “Source not found” seemingly without reason?
  27. C++ ifstream.getline() significantly slower than Java’s BufferedReader.readLine()?
  28. What different breakpoint icons mean in Eclipse?
  29. Attach debugger to application using Eclipse
  30. Eclipse Web Project Dependencies

Leave a Comment