CrystaX NDK

Violet Giraffe wrote:

I'm trying to debug native code the same way I did with the official NDK, and gdb crashes. I didn't edit any configs at all, simply replaced the NDK r10 with Crystax 10.1. Is it a known problem? Do I need to edit some settings? I don't know if it's a bug or a user error.

No, this is not known error. We need more details to help you. Please explain as detailed as possible what you did and how to reproduce the problem. Minimal project reproducing the bug would be very helpful.

Probably the latter, but I couldn't find any instruction on setting up debugging in Eclipse specifically with Crystax NDK.

There is no anything CrystaX-specific for debugging, which could not be applied to Google's NDK. Shortly speaking, it should work with exactly the same settings as used for Google's NDK.

Here's the project: https://drive.google.com/file/d/0B_uKrE3_LamxeDZ2Ry05ZTBPNjg/view?usp=sharing
It's hello-jni sample from Android NDK with debugging configured. If you place it at C:/Development/hello-jni, you won't have to edit any paths.
I don't know if I set it up entirely correctly (it's always a pain doing that), but gdb definitely should not crash - which it does in this project same as in my actual project I wanted to debug.
I've confirmed that switching back to NDK r10d lets me debug my project no problem.

Alexander Zhukov wrote:

Violet Giraffe wrote:

Here's the project: https://drive.google.com/file/d/0B_uKrE3_LamxeDZ2Ry05ZTBPNjg/view?usp=sharing
It's hello-jni sample from Android NDK with debugging configured.

Thanks, I tried to debug hellojni and it seems to be a known bug in windows version of 10.1.
Could you please try to run gdb from the command line and copy here an output?
Just start cygwin shell window, cd to the HelloJni dir and run from the command:
/ndk-gdb --verbose --force --launch=com.example.hellojni.HelloJni

Alternatively, you could try our "latest nightly build":https://dl.crystax.net/ndk/windows/current/ where we've fixed that problem (and many others) and see if the problem gone. This URL is password-protected, so I'll send credentials to you by e-mail.

Thanks, the nightly build did the trick, debugging works!