-
Notifications
You must be signed in to change notification settings - Fork 257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ndk-gdb from NDK r11c for Windows x64 can't start the debugging session - it just outputs ERROR: Failed to find running process 'com.example.native_activity' #63
Comments
If I understand correctly, this is working as intended. (although apparently undocumented after I added the optional arg to --attach). It works with --launch, right? (i.e. the bug is that --help makes it sound like --launch is the default) |
You're right, |
Also clarify the usage text. Bug: android/ndk#63 Change-Id: I05e1186549aa78a52a3a2cdb5bf2adffa81c213f
I've tried to debug the
native-activity
NDK sample with ndk-gdb script on Nexus 9 running API23 with February 2016 security updates - the script fails to start the default activity if a package process is not running on the device:--delay
option makes no difference, maybe it's not working at all:After the process for package
com.example.native_activity
is created on the device - either by hand from Android launcher or by Activity Manager commandadb shell am start
ndk-gdb script works without a problem.The issue is reproduced on other devices, too.
My Nexus 9 props:
The text was updated successfully, but these errors were encountered: