Error Package Is Not Debuggable
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and android package is not debuggable policies of this site About Us Learn more about Stack Overflow the packages marked debuggable company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags
Android Debuggable True Error
Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes
How To Access Data Folder Without Root
a minute: Sign up ERROR: Package cookbook.chapter3 is not debuggable (ndk-gdb) up vote 1 down vote favorite 1 I am reading Android Native Development Kit Cookbook. And there are sample codes in each chapter. Current chapter is dedicated to Debugging an Android NDK application with NDK GDB. But I have problems with it. The cookbook requires that AndroidManifest.xml has the android:debuggable how to access root files on android without rooting attribute of the
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the
How To Access Root Folder Android From Pc
workings and policies of this site About Us Learn more about Stack root explorer for non rooted phone Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs access android data folder from pc Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join http://stackoverflow.com/questions/23985558/error-package-cookbook-chapter3-is-not-debuggable-ndk-gdb them; it only takes a minute: Sign up Android Studio - no debuggable applications up vote 198 down vote favorite 38 I tried to debug a release version of my Android application but Android Studio failed to attach a debugger. (It could not find Android procces of my running application). Under devices console, there was only a message: No http://stackoverflow.com/questions/26593927/android-studio-no-debuggable-applications debuggable applications android gradle android-studio share|improve this question asked Oct 27 '14 at 18:03 Andy 1,89931118 add a comment| 13 Answers 13 active oldest votes up vote 554 down vote accepted You also should have Tools->Android->Enable ADB Integration active. share|improve this answer answered Jan 16 '15 at 14:48 Auras 5,69931116 31 this is also helpful for regaining adb logging if u open up Device Monitor which steals it away –trippedout Feb 3 '15 at 21:19 28 if it is enabled already enabled disabling and re-enabling also solves it –Osha Mahue Apr 22 '15 at 11:01 6 It is also important to note that you aren't running another IDE such as Eclipse. If you are, you might need to restart AS after you have closed Eclipse. –Sufian May 19 '15 at 10:55 6 Thanks! Something must have disabled this on me. It might have been Android Device Monitor. –Sam Jun 20 '15 at 4:31 1 this is now default in the current Android Studio 1.3x release, and it doesn't even get close
från GoogleLogga inDolda fältSök efter grupper eller meddelanden
cocos run output that's it's being built with NDK_DEBUG=1. The game launches on the device fine after executing cocos run however when I run ndk-gdb I get the following error: "ERROR: Could not extract package's data directory. Are you sure that your installed application is debuggable?" The output of ndk-gdb --verbose is: Android NDK installation path: /Users/nin/Downloads/android-ndk-r9d Using default adb command: /Users/nin/Library/Android/sdk/platform-tools/adb ADB version found: Android Debug Bridge version 1.0.32 Using ADB flags: Using JDB command: /usr/bin/jdb Using auto-detected project path: . Found package name: learning.cocos2dx ABIs targetted by application: armeabi Device API Level: 17 Device CPU ABIs: armeabi-v7a armeabi Compatible device ABI: armeabi Using gdb setup init: ./libs/armeabi/gdb.setup Using toolchain prefix: /Users/nin/Downloads/android-ndk-r9d/toolchains/arm-linux-androideabi-4.6/prebuilt/darwin-x86_64/bin/arm-linux-androideabi- Using app out directory: ./obj/local/armeabi Found debuggable flag: false Found gdb.setup under libs/armeabi, assuming app was built with NDK_DEBUG=1 ERROR: Could not extract package's data directory. Are you sure that your installed application is debuggable? Any idea what might be wrong? I thought building with NDK_DEBUG=1 was enough. bolin 2015-08-14 17:32:52 UTC #2 I've also added android:debuggable="true" to the android manifest.I edited build_android.py so it compiles the game with NDK_LOG=1 NDK_DEBUG=true and I can see in the output log: Android NDK: Application 'local' forced debuggable through NDK_DEBUG However I'm still getting the same error as before. This is the output of ndk-gdb --verbose: Android NDK installation path: /Users/nin/Downloads/android-ndk-r9d Using default adb command: /Users/nin/Library/Android/sdk/platform-tools/adb ADB version found: Android Debug Bridge version 1.0.32 Using ADB flags: Using JDB command: /usr/bin/jdb Using auto-detected project path: . Found package name: learning.cocos2dx ABIs targetted by application: armeabi Device API Level: 17 Device CPU ABIs: armeabi-v7a armeabi Compatible device ABI: armeabi Using gdb setup init: ./libs/armeabi/gdb.setup Using toolchain prefix: /Users/nin/Downloads/android-ndk-r9d/toolchains/arm-linux-androideabi-4.6/prebuilt/darwin-x86_64/bin/arm-linux-androideabi- Using app out directory: ./obj/local/armeabi Found debuggable flag: true ERROR: Could not extract package's data directory. Are you sure that your installed application is debuggable? So the debuggable flag is being