FATAL SIGNAL 11 (Sigsegv) at 0x00000000 (code=1)?
As mentioned by Nicola, this is most likely caused by dereferencing a null pointer in the native code. I had a similar issue and resolved it by debugging the stack trace.
If you turn off filtering in your log cat, you will see the entire stack trace. This will give you detailed information at where the crash occurred, I used the following python script in order to find the exact cause; https://code.google.com/p/android-ndk-stacktrace-analyzer/wiki/Usage
In my case a null pointer was occurring due to running a custom android build.
Good luck