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 r12 for Windows x64 can't start the debugging on arm64-v8a device #118
Comments
That's strange as it's possible to copy the same debugger binary into the package directory by hand:
|
In fact, ndk-gdb seems to not work at all for me. In case of armeabi-v7a it can deploy and launch gdbserver, but gdb executable can't connect to the gdbserver launched on the target
Here's gdb output
gdbserver.log contains a single string
|
makes sense given
you'll want to chmod a+x arm64-gdbserver. |
@enh I can, but it's makes no sense as the gdbserver that runs under the shell UID can't attach to the package process. |
Whoops, ndk-gdb is completely broken (again). |
Fixed in r12b |
This was working for me because of a local hack in adb.py in a separate checkout, which was being brought in via PYTHONPATH. :-( Bug: android/ndk#118 Change-Id: Idecbe9b1a2e914599f1c062883fe1fd72eb320f0
I'm experiencing this error message on 21.4.7075529 .
|
I've tested it on two arm64-v8a devices - one was with Android 6.0 and the other is Nexus 9 running Android N DP2, got the same result for each trial:
The text was updated successfully, but these errors were encountered: