Same problem (in Windows 7) but the cause is different.
After searching in the Environment parameters, I’ve found the evil thing named “NDK_PROJECT_PATH” which has value is an invalid path.
Deleted it and things are working again 😉
More Related Contents:
- Android Fatal signal 11 (SIGSEGV) at 0x636f7d89 (code=1). How can it be tracked down?
- Integrate MuPDF Reader in an app
- How to use 32-bit native libraries on 64-bit Android device
- Copy Database from assets folder in unrooted device
- ffmpeg for a android (using tutorial: “ffmpeg and Android.mk”)
- Eclipse compiles successfully but still gives semantic errors
- Cannot load library: reloc_library[1285]: cannot locate ‘rand’
- How to simulate touch from background service with sendevent or other way?
- Android NDK: getting the backtrace
- libjpeg-turbo for android
- How does native android code written for ARM run on x86?
- [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]
- run-as Package ‘a.b.c’ is unknown – Galaxy S4 Jellybean or Android 4.3
- Android NDK: Link using a pre-compiled static library
- CLI on DalvikVM fails on JNI lib
- Can not set debuggable flag in AndroidManifest.xml
- How to package native commandline application in apk?
- Rotating a bitmap using JNI & NDK
- Android OpenGL ES 2.0 emulator
- Official “Boost library” Support for Android and iOS? [closed]
- NDK – How to use a generated .so library in another project
- Any simple way to log in Android NDK code?
- Native libraries not found in ApplicationInfo.nativeLibraryDir when building app bundle for arm64 Android phone
- Why is redirecting stdout/stderr on android not working?
- After update android studio could not create parent directory for lock file
- Android OpenAL?
- How to start an android app with valgrind
- Position Independent Executables and Android
- Android valgrind build fails
- Access android context in ndk application